Closed Bug 280427 Opened 20 years ago Closed 20 years ago

100 % CPU hang on exit, without alert about running process

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: spam, Unassigned)

References

Details

(Keywords: regression)

trunk 3005013005 WInXP Didn't happen with the trunk build from jan 14th To reproduce - probably many ways - this one seems to be guaranteed: Start Mozilla Go to Help->About Mozilla Close the About-window Then File->Exit Mozilla Result: Open task manager and watch CPU resources: It's at 100% Check running tasks: Mozilla is still running Kill the mozilla process, and CPU usage goes back to normal I repated this 4 times with success, seems the About window is involved. Severity blocker since this nearly fried my laptop. Also noteworthy: Mozilla can be started several times after this hang, without the usual alert appearing (warning that a process already is running)
a possible hint to the hang may be found in TB i send around an hour ago. Forgot inciden number, but mail address is included
Looks like this is your Talkback report (comment and time, I can't see the e-mail address): http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=3383865#id So this looks for me like a duplicate of Bug 280456.
Summary: 100 % CPU hang on exit, without alert abt running process → 100 % CPU hang on exit, without alert about running process
Version: unspecified → Trunk
See bug 280456 comment 4, do you still see the hang?
can't download for another week - am on GPRS while on vacation
*** This bug has been marked as a duplicate of 280456 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
*** Bug 284204 has been marked as a duplicate of this bug. ***
See recent Bug 283823 and Bug 283523 too
Flags: blocking1.8b2?
Flags: blocking-seamonkey1.0a?
Up until now, there's only the reporter seeing this, and it was reopened without a comment if it is still seen. I don't think we'll hold an alpha of the new suite for that one. If this is seen more often and gets better researched (at least some further data about it happening, then perhaps you can consider to re-nominate. Unless that happens, blocking-
Flags: blocking-seamonkey1.0a? → blocking-seamonkey1.0a-
WFM - it doesn't happen in 2005032005
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.