Closed Bug 21087 Opened 25 years ago Closed 18 years ago

EventQueue destruction should not happen along with servicemanager destruction

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Milestone:
Future

People

(Reporter: dp, Unassigned)

Details

Eventqueue destruction is happening off servicemanager destruction. The problem
with this is that the GetService() from NotifyObserver() is going to fail as
servicemanager will deny any GetService() request on shutdown.

The best would be to do the eventqueue destruction on
NS_XPCOM_SHUTDOWN_OBSERVER_ID observer.


#2  0x4016b9b0 in nsServiceManager::GetService (aProgID=0x401a5980
"component://netscape/observer-service", aIID=@0x401ab628, result=0xbffff464,
shutdownListener=0x0) at nsServiceManager.cpp:547
#3  0x4016a7f7 in nsGetServiceByProgID::operator() (this=0xbffff4bc,
aIID=@0x401ab628, aInstancePtr=0xbffff464) at nsServiceManager.cpp:59
#4  0x4018f2ec in nsCOMPtr<nsIObserverService>::assign_from_helper
(this=0xbffff4cc, helper=@0xbffff4bc, aIID=@0x401ab628) at
../../dist/include/nsCOMPtr.h:768
#5  0x4018f3b1 in nsCOMPtr<nsIObserverService>::nsCOMPtr (this=0xbffff4cc,
helper=@0xbffff4bc) at ../../dist/include/nsCOMPtr.h:496
#6  0x4016d68b in nsEventQueueImpl::NotifyObservers (this=0x8896e60,
aTopic=0x401a584f "nsIEventQueueDestroyed") at nsEventQueue.cpp:105
#7  0x4016d2e3 in nsEventQueueImpl::~nsEventQueueImpl (this=0x8896e60,
__in_chrg=3) at nsEventQueue.cpp:62
(More stack frames follow...)
(gdb)
Whiteboard: needs danm triage
danm, please triage.
Summary: EventQueue destruction should happen along with servicemanager destruction → EventQueue destruction should not happen along with servicemanager destruction
This aint M12. More like beta.
Status: NEW → ASSIGNED
Whiteboard: needs danm triage
Target Milestone: M16
dp and I have discussed this. Its shutdown misbehaviour is causing some furrowed brows
in the service manager, but no noticeable damage is done. It wants to be fixed, but there's
no emergency.
Mass-moving all M16 non-feature bugs to M17, which we still consider to be 
part of beta2
Target Milestone: M16 → M17
moving to m18
Target Milestone: M17 → M18
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
Target Milestone: M21 → Future
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Updating QA Contact.
QA Contact: ckritzer → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
QA contact updated
QA Contact: gerardok → madhur
QA Contact: madhur → rakeshmishra
QA Contact: rakeshmishra → trix
Assignee: danm.moz → nobody
Status: ASSIGNED → NEW
I believe we can close this bug, now that bug 326273 is fixed.  Marking INVALID since the core problem no longer applies in the threadmanager world.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.