Closed Bug 214190 Opened 21 years ago Closed 21 years ago

Browser fails to start after splash screen.

Categories

(SeaMonkey :: General, defect)

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jasonb, Unassigned)

References

Details

(Keywords: crash, regression) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030725
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030725

With the 7/28-04 build, when running Mozilla all I get is the splash screen
coming up, going away, and then nothing.  The process remains and must be killed
manually.  This makes it impossible to start the browser.

Reproducible: Always

Steps to Reproduce:
-> Windows 2000 since reports on MozillaZine indicate this happens under both
2000 and XP.
OS: Windows XP → Windows 2000
> The process remains and must be killed manually.

I take that back.  It disappears on its own after about 30 seconds.  (I just
didn't wait long enough.)

Also, the feedback agent does pop up when this happens.  (I sent in a report,
and have also saved the data in case anybody thinks I should attach it here.)

Adding appropriate keywords.
Keywords: crash, regression
TB22268418Q on Win98, installed from todays mozilla-win32-installer-sea.exe
See recent comments in bug 208030; chances are, you're seeing that crash.
Depends on: 208030
Ditto - up to the 26th's build on win2k.
I'm running on todays build (072304) but only after three clean installs and NO
other outside theme (using Modern).

> I'm running on todays build (072304)

Was that a typo?  As of this comment, today's build is 072804...
there I go again, typing under the influence of cold meds...
The correct "today" is 072804. Still testing releases back to the 23rd so far.
Update- after reinstalling several times, 072804 crashes every time (it doesn't
matter what theme). The last release I get to work (not crash) is 072304
(Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/2003072304)
> The last release I get to work (not crash) is 072304

Strange.  Everything from 072304 to 072704 worked for me.  It was only the build
on the 28th that caused me any grief.  (Then again, you're using NT rather than
XP.)  If we have different regression dates for different OSs then things are
really messed up...
For regression testing I installed builds from 20030723 till todays build, and
with the older ones I got error messages popping up that a folder wasn´t
available, or a similar wording. I didn´t look at it, I assumed that this was a
message from windows explorer who didn´t like that mozilla uninstaller took away
its folders.

Jason, I couldn't answer your mail, because you sent me:
SMTP error from remote mailer after RCPT TO:<jasonb@dante.com>:
    host virgil.dante.com [216.221.82.6]: 550
<mailout06.sul.t-online.com[194.25.134.19]>:
    Client host rejected: No more SPAM will be accepted from your site.

So I'll give the answer here:
How to get the Talkback-ID:
Wait till the talkback record is sent, then start talkback.exe in the
Mozilla/Components directory, if you are on windows. You'll see the Talkback IDs
that have been sent with this browser, and the messages, which couldn´t be
delivered. You can try to sent them then.
> No more SPAM 

Doh!  My apologies (it's fixed now), and thanks for the note about talkback.

I doubt that the missing folder issue is the reason for the symptoms of this bug
but I could be wrong.
Different symptom from bug 214178, but same cause.  The checkin earlier today to
js/src/jsscript.c should have relieved the symptom here.  If someone can confirm
that this bug is gone with the respun builds, please close.  I didn't want to
dup this against 214178.  Probably best to close it, after confirming it was
fixed by today's checkin.

/be
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030728
BuildID 2003072813 mozilla-win32-installer-sea.exe installed fine.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Confirming that it works now.  (Fixed by fix for bug 214178.)
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.