Closed
Bug 80317
Opened 24 years ago
Closed 22 years ago
crashes at startup
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Stephen.Pickering, Assigned: asa)
Details
(Keywords: crash)
Attachments
(1 file)
2.42 KB,
text/plain
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9) Gecko/20010505
BuildID: 2001050515
Crashes at startup (all versions, zip & installer) with error
Instruction at "0x77f81b4d" referenced memory at "0x000000ac". The memory could
not be "read".
Pressing OK kills app, ignoring and it seems to run ok.
Reproducible: Always
Steps to Reproduce:
1.Start app
Actual Results: Crashes
Comment 1•24 years ago
|
||
I think a Win startup crasher was fixed a few days ago. Could you retry with a
recent build?
Keywords: crash
Comment 2•24 years ago
|
||
Reporter: this is a dupe of bug 80029 (already fixed)
Please try it again with a newer build.
Reopen if you that doens´t fix your problem.
*** This bug has been marked as a duplicate of 80029 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 3•24 years ago
|
||
Reporter: Which build crash at startup ?
If you see this problem not with 2001050515 than this is not a dupe of bug 80029
and you should try it with a new profile.
(run mozilla -profilemanager).
And if you see the crash with a new profile you should try it with a new build
(as Oliver suggests)
reopening and waiting for the reporters answer.
Sorry for the SPAM (I shouldn´t duping bugs while I´m tired)
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 4•24 years ago
|
||
I confirm for Win98
I downloaded the installer from
http://ftp.mozilla.org/pub/mozilla/nightly/latest/ last night just at midnight
right coast time. It died upon launch.
I just completed DLing mozilla-win32-installer.exe 11-May-2001 23:27 7.8M - the
current lastet - and the problem persists. It is dying just after the flaming
Moz flash frame. I did try to launch the profile manager aslo with the same
result.
Comment 5•24 years ago
|
||
Confirming as per Ben's comments.
Stephen, Ben, could you provide a stack trace or talkback ID?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•24 years ago
|
||
Comment 7•24 years ago
|
||
I installed with the quality feedback option, where do I find the talkback id?
98 doesn't have a DrWatson, is there an equivalent file I can find?
Comment 8•24 years ago
|
||
build id: 2001051208
now working for me on Win98
Reporter | ||
Comment 9•24 years ago
|
||
Have tried various release, final version is build ID: 2001051220, still
crashes, message has changed slightly (new location):
Instruction at "0x77f821e1" referenced memory at "0x000000ac". The memory could
not be "read".
Again, ignoring application error and Mozilla seems to work, but press the OK
on the error dialog and mozilla crashes.
I will today's download when available.
BTW: Works on another machine I use.
Assignee | ||
Comment 10•24 years ago
|
||
If you crash and talkback picks up the crash it will assign the incident an ID.
You can get the incident ID by re running the talkback.exe. Please attach the
IDs here. Also, if you cannot get the ID please post teh email address you
included in the report and the time you sent it. TH=hanks.
Reporter | ||
Comment 11•24 years ago
|
||
Just had a cable modem installed, had problems getting dhcp going so completely
removed ZoneAlarm, guess what, Mozilla works !
Re-installed Mozilla release 0.81.
ZoneAlarm v2.6 was disabled, but installed, don't know if it would be a problem
if it were running ?
I have a firewall now so I don't need ZoneAlarm.
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 12•22 years ago
|
||
This is resolved incorrectly.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•22 years ago
|
||
-> WFM.
Someone please mark this verified.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•