Closed
Bug 281885
Opened 20 years ago
Closed 20 years ago
FF crashes if you close about:plugins with the source view of that page open
Categories
(Toolkit :: View Source, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jaas, Assigned: bugs)
Details
Firefox 1.0, Mac OS X 10.3.8: 1. Load about:plugins 2. View the source of that page so it shows up in a new window 3. Close the page displaying about:plugins, leave the source view open 4. Crash
Pertinent part of the crash log: Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x7c621b78 Thread 0 Crashed: 0 libobjc.A.dylib 0x90831214 objc_msgSend + 0x34 1 com.apple.AppKit 0x92fce8fc carbonAppWindowCloseHandler + 0x6c 2 com.apple.HIToolbox 0x927d1fa0 DispatchEventToHandlers + 0x150 3 com.apple.HIToolbox 0x927d2214 SendEventToEventTargetInternal + 0x174 4 com.apple.HIToolbox 0x927d6694 SendEventToEventTargetWithOptions + 0x28 5 com.apple.HIToolbox 0x9281b104 WindowData::Destruct() + 0xcc 6 com.apple.CoreFoundation 0x90190cf0 CFRelease + 0x1e8 7 org.mozilla.firefox 0x001bf8c8 _ZN11nsMacWindowD4Ev + 0xf4 8 org.mozilla.firefox 0x001d6ed0 nsBaseWidget::Release() + 0x44 9 org.mozilla.firefox 0x001d5298 nsMacMessagePump::DispatchOSEventToRaptor(EventRecord&, OpaqueWindowPtr*) + 0x6c 10 org.mozilla.firefox 0x001d456c nsMacMessagePump::DispatchEvent(int, EventRecord*) + 0xb0 11 org.mozilla.firefox 0x001d438c nsMacMessagePump::DoMessagePump() + 0x40 12 org.mozilla.firefox 0x001bb910 nsAppShell::Run() + 0x38 13 org.mozilla.firefox 0x007ebc18 xre_main(int, char**, nsXREAppData const*) + 0xac0 14 org.mozilla.firefox 0x0000f54c start + 0x1b0 15 org.mozilla.firefox 0x0000f3cc start + 0x30
Comment 2•20 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050227 Firefox/1.0+ I followed your recipe and did not get the crash. How reproducible is the problem?
can't repro any more, probably a fluke
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•