Closed Bug 99371 Opened 24 years ago Closed 24 years ago

http protocol handler created before XPCOM is initialized

Categories

(SeaMonkey :: UI Design, defect)

Product:
SeaMonkey
Component:
UI Design
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: danm.moz, Assigned: bugzilla)

Details

nsNativeAppSupportWin.cpp around line 933 was looking in the Windows registry to see whether -turbo mode should be enabled. To do this it was getting the http protocol handler service, but before XPCOM had been initialized. Oddly, things mostly still worked, but this did cause at least one smoketest blocker. dp and I have just commented out the offending code. Since we broke the -turbo check, I figure we should let people know and to please do it slightly differently next time.
Is there a current defect that needs fixing here, or is this just a note?
the code that was commented out was part of the implementation of -turbo mode.
Okay thanks. So...fixed now, isn't it?
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Well, the code's still gone, so I'm happy. If you don't mind the missing functionality (or if it's been placed in a better home), then yeah, it's fixed. (Note to verifiers: the code commented out was causing an assertion at startup (COM was being initialized twice), so it would be obvious if it had come back.)
Status: RESOLVED → VERIFIED
Well...hrm...I assume it got fixed because turbo really wouldn't be working otherwise. But let me reopen to remind myself to check and be sure.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
fixed.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
rs vrfy
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.