Closed Bug 55187 Opened 25 years ago Closed 25 years ago

Crash on startup

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: ken, Assigned: asa)

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (WinNT; U) BuildID: Upon startup, splash screen comes up, then dialog saying The instruction at "0x60c71419" referenced memory at "0x00000001". The memory could not be "read". Reproducible: Always Steps to Reproduce: 1. Start Netscape6 PR3 Actual Results: crash Expected Results: no crash The same behavior has been occurring for me on the last month or so of nightly builds.
*mass spam* adding crash keyword to all crash bugs
Keywords: crash
Ken, have you followed the updating procedures? (Del users50 dir, bin dir, and %WINDIR%\mozilla*.dat) I ask because I've had no problem with any of the recent builds.
Jake, I had been deleting the bin dir and %WINDIR%\mozilla*.dat (and %WINDIR%\Profiles\kgeis\Application Data\mozilla) but I hadn't been deleting Users50. Tried it again after cleaning all of those, and I still get the error.
Hmmm.... I assume you're using a recent build... unfortunately (for you, fortunately for me) I can't reproduce this bug. Because of that, I can't confirm it (make it NEW). I've used recent Mozilla builds sucessfully on almost all Win32 platforms. I had also forgot that profiles had moved to %WINDIR%\Profiles\%USER%\Application Data\mozilla
are you still using pr3?
I got rid of PR3 on my machine and unzipped a recent build (10/17 or 10/18) before I last tested it.
Ken Geis, did you delete the mozilla profile directory in %WINDIR%\Profiles\%USER%\Application Data\ and test this again?
Yes, I cleaned up everything before my last test.
ken@xigo.com - could you please download a talkback build (they have "talkback" in the name), reproduce this bug, and then post the incident report number here? That'll make it much easier to see what's going on. Also, seeing as you are running NT, what does Dr Watson say? Thanks :-) Gerv
Gervase: No can do! I would have done this instead of logging it through bugzilla. However, since this exception is trapped, neither Talkback nor Dr. Watson will collect this info. The only way for me to get this info is to actually build Mozilla and run it through a debugger, which I'm not prepared to do.
did you kill moz*.dat in our windows dir?
Doron: Of course I did! > Yes, I cleaned up everything before my last test.
I changed nothing about my "try out a new build" routine, but today's build works for me.
Marking WORKSFORME per the reporters above comment. BTW, Ken... I'm glad it works for you now... enjoy.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
sorry abotu being persistent, but most people forget to delete something or another, was just checking. verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.