Closed
Bug 294855
Opened 20 years ago
Closed 17 years ago
Browser crashes twice with reproducable results
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: the.go0m, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.7) Gecko/20050428 Ok heres the scoop, im running gentoo x86_64 with mozilla (see version above). I ran mozilla under gdb and from the command line with strace to get the errors i am experiencing and heres the GDB output of both when they crash. Error (1) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 27957)] 0x00002aaab4ca0c40 in Button::getButtonRecords () from /usr/lib/libflash.so.0 Error (2) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 27975)] 0x00002aaab4cacfd3 in CInputScript::GetBits () from /usr/lib/libflash.so.0 Error (3) *** glibc detected *** corrupted double-linked list: 0x000000000120ec70 *** I also saw a double free() error. But havent been able to reproduce it reliably. I do NOT have flash installed, i am running a native 64bit linux system, with IA32 compatibility support in the kernel. Reproducible: Sometimes Steps to Reproduce: Goto the URL i listed above Actual Results: crashed! Expected Results: shown the page!
Comment 1•20 years ago
|
||
> I do NOT have flash installed
then what, exactly, is /usr/lib/libflash.so?
what does about:plugins say?Assignee: general → nobody
Component: General → Plug-ins
Product: Mozilla Application Suite → Core
QA Contact: general → plugins
Version: unspecified → 1.7 Branch
Comment 3•17 years ago
|
||
Good grief. You're running Gentoo, you don't have flash, but you're crashing in libflash.so. Most. INCOMPLETE. Bug. Ever.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•