Subj : Re: What resources can an app leak permanently? To : Geo. From : Randall Parker Date : Sat Mar 31 2001 06:23 am From: Randall Parker On Thu, 29 Mar 2001 19:41:50 -0500 esteemed Geo. did'st hold forth thusly: > One test you could try, next time you can't restart it, try changing the > video resolution then see if you can restart it. (without rebooting). I'll try that. Here's another and stranger data point: I was running in JBuilder and was debugging a target process that was doing lots of graphics stuff (albeit the target process was set to invisible since I don't want to show it till its done drawing). Anyway, I happened to try to start Mozilla and Moz showed up on the task list but not even its initial splash screen showed up. Its like it was blocked at some early stage of its initialisation process. So then I killed the JBuilder target app that was doing the graphics and suddenly up popped the Moz splash screen and Moz finished booting up. So Moz was actually blocked on an OS call waiting to return from that call. I'm guessing it was a graphics rendering call for the splash screen. But that call was blocked indefinitely. Then when JBuilder killed the javaw.exe process some resource became available and Moz's OS call was able to complete. How weird. --- BBBS/NT v4.00 MP * Origin: Barktopia Gating Project http://HarborWebs.com:8081 (1:379/45) .