Closed Bug 112432 Opened 23 years ago Closed 23 years ago

locked history.dat file causes Mozilla to crash on startup

Categories

(Core Graveyard :: History: Global, defect)

Product:
Core Graveyard
Component:
History: Global
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: gsa, Assigned: bugzilla)

References

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/4.79 (Macintosh; U; PPC) BuildID: 2001112804 if you lock history.dat file Mozilla will crash on startup Reproducible: Always Steps to Reproduce: 1. in Finder select Get Info from File Menu 2. check the locked button to lock history.dat file 3. startup Mozilla Actual Results: Mozilla won't start, crashes at startup Expected Results: Mozilla should have started macsbug dump Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 01E260E4 03A48F30 PPC 01E10AC8 main+00134 03A48ED0 PPC 01E0FEE0 main1(int, char**, nsISupports*)+00BA4 03A48D00 PPC 0636D150 nsAppShellService::Run()+00018 03A48CC0 PPC 0632D77C nsAppShell::Run()+00048 03A48C70 PPC 0632E1CC nsMacMessagePump::DoMessagePump()+0003C 03A48C20 PPC 0632E620 nsMacMessagePump::DispatchEvent(int, EventRecord*)+ 00170 03A48BD0 PPC 072745A4 Repeater::DoRepeaters(const EventRecord&)+00030 03A48B90 PPC 0631B8A4 nsMacNSPREventQueueHandler::RepeatAction(const EventRecord&)+000 0C 03A48B50 PPC 0631BAE0 nsMacNSPREventQueueHandler::ProcessPLEventQueue()+ 00060 03A48AE0 PPC 06529A54 nsEventQueueImpl::ProcessPendingEvents()+00038 03A48A70 PPC 0657F5E4 PL_ProcessPendingEvents+00088 03A48A30 PPC 0657F768 PL_HandleEvent+00020 03A489F0 PPC 06246188 nsARequestObserverEvent::HandlePLEvent(PLEvent*)+ 00020 03A489B0 PPC 06246EA8 nsOnStartRequestEvent::HandleEvent()+00034 03A48960 PPC 06254E74 nsHttpChannel::OnStartRequest(nsIRequest*, nsISupports*)+0009C 03A48910 PPC 0624C700 nsHttpChannel::ProcessResponse()+001B4 03A48880 PPC 0624EF9C nsHttpChannel::ProcessRedirection(unsigned int)+ 007D0 03A48630 PPC 061A5264 nsDocLoaderImpl::OnRedirect(nsIHttpChannel*, nsIChannel*)+0023C 03A48570 PPC 061A4704 nsDocLoaderImpl::FireOnStateChange(nsIWebProgress*, nsIRequest*, int, unsigned int)+001B8 03A48480 PPC 05C1D52C nsDocShell::OnStateChange(nsIWebProgress*, nsIRequest*, int, uns igned int)+003A8 03A483B0 PPC 058AE994 nsGlobalHistory::HidePage(const char*)+00040 Closing log
-> Histroy This is not a blocker (You should read http://bugzilla.mozilla.org/bug_status.html#severity)
Assignee: asa → blakeross
Severity: blocker → critical
Component: Browser-General → History: Global
Keywords: crash
QA Contact: doronr → claudius
Blocks: 113025
still experiencing this bug in mozilla 0.9.8 release build id: 2002020405 here's macsbug output Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 3F61FFC0 07631480 PPC 3F60F978 07631420 PPC 3F60F0D0 076312A0 PPC 3E472E18 NSGetModule+014A8 07631260 PPC 3E43BEC8 NSGetModule+0C8C8 07631220 PPC 3E43C4FC NSGetModule+0CEFC 076311D0 PPC 3E43C8A4 NSGetModule+0D2A4 07631190 PPC 3F792990 Repeater::DoRepeaters(const EventRecord&)+00030 07631150 PPC 3E42D7DC 07631110 PPC 3E42D958 076310C0 PPC 3E206F68 NS_NewAdapterEnumerator+00D08 07631060 PPC 3E246CF8 PL_ProcessPendingEvents+00088 07631020 PPC 3E246E1C PL_HandleEvent+0001C 07630FE0 PPC 3E551D8C NSGetModule+3AEBC 07630FA0 PPC 3E552694 NSGetModule+3B7C4 07630F60 PPC 3E55DFFC NSGetModule+4712C 07630F20 PPC 3E557290 NSGetModule+403C0 07630ED0 PPC 3E5595CC NSGetModule+426FC 07630DD0 PPC 3DED66F4 NSGetModule+02F64 07630D60 PPC 3DED5D8C NSGetModule+025FC 07630CD0 PPC 3DE62898 07630C00 PPC 3D5ECDAC
Is this still an issue? I fixed on such possible crash while fixing bug 84766. I have since been able to browse for hours with an unreadable, unwritable history file.... (on Linux, mind you).
Ok i'm running mac os 8.6 96 mb/ vm on. I have build 2002 05 23 05. I've locked the history.dat but mozilla still successfully starts up. Maybe it's only in 9.0+. Good luck trying to fix it
WorksForMe using Mac/2002052305 (1.0).
Reporter has not responded in several monthes. There are reports that it is working. Resolving as worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.