Has anyone noticed that when focus is lost for awhile, Zquest in Large mode crashes when selected?
It's happened to me about three times already today; I'm wondering if it has to do with memory leaks.
Lost focus crash [704]
Can anyone else confirm?
I've had it crash on me as well, but I'm not using large mode, I'm using scale x 3. :shrug:
This has happened me once or twice, over a period of a month. It's a bug, certainly, but I can't pin down any triggers.
Edit: What compiler do you use? It might be profitable to distribute versions with debugging symbols enabled, so that crash logs can be used.
I can confirm. This happens to me about twice a week.
EDIT: A very "reliable" trigger for a program crash is bringing ZQuest to the front while a browser page is opening. Crashes every time.
I think I know what's causing it. Because of its massive need of memory, it gives some away when it goes idle. However, when another program is also using a large amount of memory (such as a Web browser), and you switch to ZQuest, the amount of memory it needs goes up immediately. However, when it can't get the required amount of memory, it has no choice but to crash instantly.
Hope this helps.
EDIT: Just read above. This makes my theory the only plausible reason right now.
Linkus, how much memory and free hard drive space do you have?
On this computer...
863 MHz Intel PIII Processor
384 MB RAM
Hard Drives:
C:\ - 18.6 GB, 2.29 GB free
F:\ - 32.7 GB, 21.6 GB free
Thumb Drive (the copy of 704 I'm using is on this)--1.9 GB, 558 MB free
Laptop:
1.8 GHz (2.2 Overclocked) Intel P4 Processor, 229 MB RAM
C:\ - 11.6 GB, around 5.8 GB free
Crashing is not as frequent on the laptop; only once or twice in a week.
The Windows kernel is bad, but it's not *that* bad. You would get an error message saying, "Windows is running out of swap space, please delete files on drive C:\", or something to that effect, before randomly starving applications of memory.
Can you do additional tests? Put a varying load on your RAM, and see if there's a certain level at which ZQ always crashes?
I wouldn't be too surprised if it's just Allegro having buggy focus-switching code.
Just got hit by this bug; it's caused by some of the menu-drawing code not bounds-checking before drawing some parts of the menu, causing some of the parts of the menu to be drawn out of the bounds of the screen, causing Allegro to become very upset. Fixed in the next build.
Confirmed fixed. Good work, I no longer have to worry about switching to ZQ too fast and losing progress. :thumbsup: