13:26:58 <+luckz> can I get anybody with an intel cpu and XP to help me for a few minutes?
13:29:50 <+luckz> task manager -> processes -> view -> select columns -> GDI objects
13:32:50 < descenterace> yes?
13:33:16 < descenterace> what about it?
13:35:13 <+luckz> 1) how many are you using?
13:35:23 < descenterace> which process?
13:35:28 <+luckz> in total
13:35:31 <+luckz> and what uses most.
13:35:42 < descenterace> vmware uses most (around 600)
13:35:56 < descenterace> guess this box is using about 2000 total
13:36:22 < descenterace> why?
13:36:23 <+luckz> 2) if you just use IE and open a billion tabs in it (IE7) or create a billion new windows (IE6), does everything explode at around 10k used
 gdi objects? (note: explodation can be undone with closing tabs again; explodation manifests itself with right-clicking not working, among other things)
13:37:35 < descenterace> well... IE actually just stopped at around 40 windows
13:37:40 < descenterace> that's 2200 objects
13:37:47 < descenterace> or 50MB
13:38:12 <+luckz> so you mean it didn't feel like doing more and then created one that was basically a large blob of white with missing content?
13:38:32 < descenterace> that's right. the last one was an empty window
13:39:00 < descenterace> and this is an AMD computer :p
13:39:02 <+luckz> oh
13:39:26 < descenterace> don't have an intel box handy but i was curious about your question
13:39:44 <+luckz> well, I'm basically trying to find out if intel-based comps do that too
13:39:50 < descenterace> ah, right
13:40:16 < descenterace> i'd guess it's an IE bug, but it could just be Windows capping the number of GDI handles it gives out to apps
13:40:31 <+luckz> it does not depend on IE being used.
13:40:41 <+luckz> IE just is good at eating GDI for breakfast.
13:40:44 < descenterace> ah. so it's a Windows limit
13:40:54 <+luckz> limit by default is set to 10k.
13:41:16 <+luckz> you can increase it to 16.something k in 2000; dunno what you can set it to in XP - somebody on a forum claimed 18k
13:41:18 < descenterace> yeah, so the 'exploding' is caused by the app waiting for more handles
13:41:28 <+luckz> more handles never appear
13:41:35 < descenterace> exactly
13:41:41 <+luckz> and I doubt it actually resumes functioning if more handles appear due to other stuff being closed
13:41:50 <+luckz> I think such a 'broken' tab/window always has to be closed
13:42:09 < descenterace> likely just an unhandled error condition that no one expected the software to encounter, then
13:42:36 < descenterace> but when are you ever seriously going to use that many GDI handles?
13:42:41 <+luckz> mine also for some reason beeps when I go past 3k
13:42:45 <+luckz> happens reasonably often.
13:42:52 <+luckz> otherwise I wouldn't be trying to fix it.
13:42:55 < descenterace> any app doing that much graphical stuff should probably be using DirectX or something.
13:42:57 <+luckz> also happens on several comps.
13:43:05 <+luckz> just starting photoshop often was enough on my old comp
13:43:09 < descenterace> how in the HELL do you get to 10000 GDI handles?!
13:43:10 < descenterace> ouch
13:43:50 <+luckz> and yes, I just checked again, a 'broken' tab does not ever fix itself
13:44:07 <+luckz> at least it doesn't stop being a white blob.
13:44:12 <+luckz> it eventually reacts to ctrl-w.
13:44:17 < descenterace> bloody hell, even the Gimp v2 doesn't guzzle more than 200
13:46:29 <%Headphones> 10k GDI = bluescreen
13:47:09 <+luckz> I don't think I can bluescreen with 10k. my box just doesn't let me get anywhere anymore once i reached enough for it to break rightclicking etc.
13:47:36 <%Headphones> i found that my wifi control app was using 9.999k
13:47:39 <%Headphones> GDI obj
13:47:43 <%Headphones> which was what was fucking my pc