Page 2 of 2

Re: "Not Responding" when I leave PureBasic?

Posted: Thu Aug 20, 2015 12:56 pm
by HanPBF
Just an idea...
I had annoying IDE crashes and even a not-starting-IDE when the PC has an admin and a user account.

Some IDEs like Delphi, VB6 are only fully running in admin mode.

Re: "Not Responding" when I leave PureBasic?

Posted: Sun Aug 30, 2015 5:01 pm
by freak
The delay is probably caused by the session history feature. It needs to write events to the database for the files you have open when you close the IDE. Unfortunately, the events have to be processed in order, so it cannot be parallelized. Although I do not understand exactly why it takes so long for some people. Here it works quite well even with larger files.

I have added a small window to indicate that the saving is in progress, so there shouldn't be a "not responding" any more.

Re: "Not Responding" when I leave PureBasic?

Posted: Mon Aug 31, 2015 5:03 am
by collectordave
just noticed this

After running a few example progs and some of my own trials not all closed correctly and left a process running in task manager. Which i had to kill manually. Do not know the extent of this or even if it is a problem as using VB sometimes has the same effect.

I have had no issue with PB taking a long time to close as i only work on one or two files at a time and regularly close the ones i do not need.

Re: "Not Responding" when I leave PureBasic?

Posted: Mon Aug 31, 2015 8:37 am
by IdeasVacuum
The solution is as Danilo described, close and then just wait a few seconds.

I think it is very likely that Windows Defender or other AV is checking the database activity, which would certainly slow it down. I am using AVG at the moment and it kicks-in roughly once per hour and locks-up the PC for around 2 seconds if any 'heavy' process is running, including but not only PB.

The "Not Responding" message is just lazy coding by Microsoft, they are using that message in an inappropriate way - you can see via Task Manager that the "Not Responding" application is processing - I think they should at least start with a "Busy" message, and also stop changing the cursor graphic too - that just alarms the inexperienced/casual PC User.