PureBasic Forums - English

Hi,
After loading and working (or not) with PureBasic 5.1 32 or 64 bit, if I want to leave or close PB, I have to force close the task manager? I'm running Windows 7.
If someone has an idea? thank you,

En français !
Après avoir chargé et travaillé (ou pas) avec PureBasic 5.1 32 ou 64 bits , si je veux quitter ou fermer PB, je suis obligé de forcer la fermeture par le gestionnaire des tâches ? Je suis sous Windows 7. Ou se trouve l'erreur ?
Si quelqu'un a une idée ? Merci.

Can't reproduce it. I ran task manager, called up PB, PureBasic.exe appeared in the process list, closed PB and it disappeared from the list. All seems well here, Windows 7 PB 5.10 final.

same same

Works fine here
windows 8 x64 using pb5.1 32bit

Ok, this is probably a problem installing PB 5.1 or with my windows 7 (64) while I installed PureBasic 32?
I'll try uninstalling and reinstalling ... and see what happens!
Thank you to you ...
PS: I will inform you if I find something.

any news ?

I don't know if this is helpful but I've noticed it takes longer to close PB now in 5.10 once I click X it takes a second or two before it closes.
Win 7 64 bit

Nubcake wrote:I don't know if this is helpful but I've noticed it takes longer to close PB now in 5.10 once I click X it takes a second or two before it closes.
Win 7 64 bit

11 seconds here for closing the IDE with many opened files. "(not responding)" is added to the window title by Windows.
It closes correctly here, but maybe the event queue gets full on other OS, if not checking events for several seconds.

It does the same on OS X, a few seconds to close the IDE when many files are opened, however, this does NOT happen when you disable session history. Maybe it's linked to the problem gebonet is facing?

Danilo wrote:

Nubcake wrote:I don't know if this is helpful but I've noticed it takes longer to close PB now in 5.10 once I click X it takes a second or two before it closes.
Win 7 64 bit

11 seconds here for closing the IDE with many opened files. "(not responding)" is added to the window title by Windows.
It closes correctly here, but maybe the event queue gets full on other OS, if not checking events for several seconds.

I just tested it with 21 new empty files it took 3 secs to close.

Nubcake wrote:I just tested it with 21 new empty files it took 3 secs to close.

Usually I don't care, but I just checked now: 99 opened files here, all different sizes (real world source codes).
Starting the IDE requires 22 seconds here, 11 seconds for closing it.

I just mentioned it because it could be the problem GeBonet has. I press the close button of the window here
and nothing happens for 11 seconds. After 11 seconds the PB IDE window closes. Sometimes window title
changes to "(Not Responding)", so if I would press close again and again, it could trigger the task manager
for ending the process. I know it is slow, so I just press close one time here and everything ends correctly
after the 11 seconds.
For the user experience, it is unusual that I press the close button of an application and nothing happens
for 11 seconds. Other apps don't do that, they would close/hide the window instantly and save the
history database in the background.

Generally not a problem for me, all-thought I think some things could be improved:
The most funny thing is, the start-up splash screen is in the background, behind the main IDE window at start-up.
Makes the splash screen redundant, as I don't see it at the 22 seconds IDE start-up. Bringing it to foreground
does not work, because the IDE brings itself to foreground after loading of every file (99 times at start-up here).

Another thing is IDE start-up seems to use only one single thread. Could be made faster for an Apple Mac Pro with 12 cores.
Looks like PB is parsing every loaded file at start-up and doing syntax highlighting. Does not make sense, because I see only
1 file after start-up has finished, so only this 1 file really requires instant syntax highlighting. Other files could be parsed later
(maybe in background or when switching to those sources), or at least the parsing could be done in threads, so it could be up to 12 times
faster on current machines, at least 64 times faster in the near future.

While we are at it, parsing in the IDE seems to be very slow generally. Working with a 9,000 lines file is not really fun, as
pressing <Return> takes 1 second for inserting every new line. Loading of the same file takes also 7 seconds (358kB, 8.718 lines to be exact).
I have the feeling this could have to do with extensive usage of Macro's.
I am used to it, so I don't want to complain. Just saying what my experience is. Maybe some things could get improved in the future,
after the chiefs heard about it.

It is such little things that make the difference between premium class cars and the cheapest cars.

Just tried with 42 files, and it seems OK when closing (less than 1 secs). Can anybody confirm ?

The IDE is pretty slow with closing files. It's not 11 seconds as mentioned here, but it is noticeable.
Also the IDE doesn't respond during that time so it might "white-out" until it's finished.

I loaded up around 60 files, and closed out of PureBasic. It was around 3-6 seconds, but it did exit out fully and disappeared from Windows Task Manager processes list.

Some things to consider, computer specs, number of files loaded ... likely influence the time.

It looks like PB is closing all tabs one by one as it takes roughly the same time as holding Ctrl+W.
I don't know what kind of clean-up work the IDE needs to do but it seems like it might be enough
if PB just "hard-closed" everything if there are no unsaved files.