My apologies, I cannot contribute any specifics, especially because Mozilla did not crash. However, I have never had this type of lockup _on system startup_ during the last 4 years of daily use on this computer before I enabled the Mozilla -turbo mode. 256Mb RAM in a AMD K6-2 300MHz, a slow machine by today's standards, a config where -turbo makes sense. Build ID: 2001090703 I would think there is an 80% chance that Mozilla caused this - I had removed alll other programs on startup, so there was absolutely nothing (not even a virus checker) except about 5 Windows explorer windows and the system monitor that showed an idle CPU.The symptom of the lockup is beeps on mouse movements and keyboard input - Ctrl+Alt+Del did not work, I had to turn power off.

from asa to selmer for reassignment and diagnosis. nsbranch until we learn more.

Chris, please send these direct to Peter for fastest turnaround.

Can QA or anyone else reproduce this? ->law, p1/094

nsbranch

Adding dp to cc: list. dp, this looks different from 88844, right? Since we're in Windows startup, we've got the -turbo flag and we're not hitting the xpcom init problems (or so I figure). Any ideas?

No ideas here. Can the user try it with a newer build ? Does this happen consistently ?

nothing actionable here, resolving as invalid. Please reopen with exact steps to reproduce if you see this again.

removing blocker status to bug 75599 and bug 99488, since INVALID shouldn't block.