Closed Bug 178888 Opened 23 years ago Closed 23 years ago

todays nightly hangs on startup (not 178874)

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jmd, Assigned: asa)

Details

(Keywords: hang, regression)

Fresh profile or not, todays Linux nightly hangs on startup. Yesterdays still works fine on this system. Strace showed it to be polling fd 9/sleeping, but I couldn't find what 9 was.
I'm seeing this also (2002110708). CVS (debug) from 8:26AM works fine. 2002110604 nightly worked fine. stack from the nightly is: #0 poll () from /lib/i686/libc.so.6 #1 g_main_poll () from /usr/lib/libglib-1.2.so.0 #2 g_main_iterate () from /usr/lib/libglib-1.2.so.0 #3 g_main_run () from /usr/lib/libglib-1.2.so.0 #4 gtk_main () from /usr/lib/libgtk-1.2.so.0 #5 NSGetModule () from components/libwidget_gtk.so #6 fullsoft_copyright () from components/libnsappshell.so #7 0x0805149e in getCountry () #8 0x08051caf in main () #9 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
Severity: critical → blocker
Keywords: hang, regression
I can confirm this with optimized build. When debug is enabled everything works fine.
You can try looking in /proc/<mozilla_pid>/fd and see if fd 9 rings any bells.
I had the same problem on my own CVS build (2002-11-07-05 for Linux). I made a new build after pete.zha@sun.com had backed out his changes: 11/07/2002 09:18 pete.zha%sun.com back out for bug 144664, a=cls and that build works so the backout seems to fix this problems for me.
This is probably the blocker bug from this morning (bug 178879). The offending checkin was backed out, and that was marked fixed.
saw the same hang and later crash. Repulled CVS - and mozilla starts fine again now. (Linux) WFM.
I did a CVS update as suggested in comment #4 and now it works again (cvs/trunk/Linux). Marking WFM.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.