Closed Bug 3357 Opened 26 years ago Closed 26 years ago

sproadic problems - grey window after long wait, then nothing else

Categories

(Core :: XPCOM, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sar, Assigned: dp)

Details

We've seen this sporadicly on WinNT, Win98, Linux. We've seen it mostly in opt builds, but occasionally in debug builds as well. The problem - When I launch apprunner or viewer on WinNT (opt build) I get a title bar, and the outline of the window, but no toolbar, no content, no chrome, nothing. You can still see the background behind the window (like it's clear) When Chofmann ran the same bits on his win95 box, he was able to get fully rendered screens, browse, etc. Peter Trudelle has noticed the same problem on Win98, only he actually gets a grey window instead of a clear window. On Linux, we see the grey window sometimes, we get really slow response at other times, and in general it's not predictable. This affects apprunner only on linux as far as I know. Dp just looked at this and said on my machine it looks like it's passing the autoregistration stuff with flying colors but then running into major performance problems. I'm still assigining this him in the hope that he can help figure out what is really going on.
Status: NEW → ASSIGNED
To improve performance, waterson implemented a ProgID cache in the repository. That didn't help. I am not seeing it myself. I am suspecting the creationg of zillions of objects as the probably cause. I need to test my theory out.
Caching ProgIDTOCLSID() and commenting the call to CLSIDToProgID() before doing the NSGetFactory() got performance back up. Waterson is implementing this. Waterson, once you checkin add comments to the bug please. I am going to keep the bug assigned to me as I am doing some more analysis.
Component: Registry → XPCOM Registry
Product: MozillaClassic → Browser
If this problem occurs with a "unable to create text converter for mime type text/xul" message, then this probably has something to do with registry corruption or the failure of the RDF DLL to be registered. Otherwise, I have no clue. If we could isolate it and make it more reproducable, that would be good.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This should be fixed with the slew of registry problems that we fixed.
actually we still this, it happened in 3/15 and 3/16 builds and it is sporadic. It seems to happen more after I have done a fair amount of testing, maybe leaks are causing the problem. We did get this to happen on Linux and win95. I haven't sat in front of winNT or win98 or mac to check it out -- but we will.
QA Contact: 3849
Status: RESOLVED → VERIFIED
been working on the 3/23 build on various platforms and can't reproduce this anymore, marking as verified
Component: XPCOM Registry → XPCOM
QA Contact: rubydoo123 → xpcom
You need to log in before you can comment on or make changes to this bug.