Quote from: jo on October 03, 2008, 10:39:10 PM
Hi Brian,
It looks to me like a bit like you're running out of memory. I don't think the problem is a GDI leak because from the Process Explorer it seems like the number of GDI handles being used is about what I would expect.
Can you please pack up all the files used in your scene and email them to me, or if it's getting close to 10 MB could you please upload them somewhere and send me a link? I'd like to try your scene with the Mac version and the Windows version.
Regards,
Jo
Jo,
It's possible it could be a low memory issue within Terragen 2 itself. But, the operating system as a whole has 4G installed, only 1.6G of which was in use at the time TG2 was running (1.5G of it being TG2). So, if it had been a global system memory issue (which I'm not sure if that's what you mean), then I would have had troubles with other applications. However, that wasn't the case. At the time TG2 was running, I copied the screen shots to the clipboard, launched the Gimp to create the attached jpeg images, pasted them from the clipboard into the Gimp, saved the files and exited all without any GUI troubles. In other words, there was plenty of system memory available for launching other tasks on the system above what TG2 was doing.
Also, while the VM memory was approaching the 2GB limit (2,056,268K) , it hadn't actually reached that point (unless the limit is slightly less than (1024^2)*2). The Working Set (which is the actual memory in use by the app) was 1.5GB at 1,524,536K (still .5 GB under the 2GB ceiling). Also, while the handles may have been under what you would have expected at 373, I'm still not discounting GDI issues. In the past, when I've seen apps lose buttons, menus and other GUI interface controls, I've found this related to GDI troubles when the system still shows ample ram. But, a low memory situation could cause both the GDI issues and the threads to crash.
Of course, I don't know how Windows counts memory towards to 2GB limit. If it's only what's in the working set, then it was well under that limit. However, if it tallies in vm + working set, then total memory use would have been well over 2GB.
After reading more about GDI, I found that GDI allocates its objects from the kernel memory pool which comes from paged pool memory. So, I would have to assume that the paged pool memory is running out and GDI can't create new objects. Considering that the VM maximum was so close to the 2GB limit (and possibly even fragmented), there may not have been enough memory space left to create new GDI objects. It does appear, though, that Vista is isolating each app from one another. So, while one app may run out of internal space, it doesn't appear to affect the rest of the OS or other apps.
As soon as I get home, I will upload my project, but it will take me a little bit of time to gather up all of the pieces (models, textures and whatnot).
Thanks.