Summary: | www-client/mozilla-firefox-bin-3.0.5 + X11 killed by URL | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry S. Makovey <dmakovey> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://wiki.zimbra.com/index.php?title=Ajcody-Notes | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitry S. Makovey
2009-02-05 22:02:59 UTC
Can't confirm that. Works fine here on a mostly similar system. Looks like X is getting killed because of high memory usage - how much RAM does your system have? What does dmesg say afterward? What does /var/log/Xorg.*.log say? I'm guessing this page fro this bug causes a crash too? http://bugs.gentoo.org/show_bug.cgi?id=253062 I'm going to try opening link from comment #2 on my office machine and see if it'll crash it. However reading through bug #253062 it looks awefully like my experience. And I know I should not be running out of memory - nothing hoggs the memory that fast. it's a 1.5G machine with 2G swap. It should spend some time thrashing the swap first, no? In my experience - it's instanteneous: click-DEAD. Looks like a crash in X11 libs someplace as it crashes Xorg and everything else naturally goes with it (KDE/FF/etc.). I'll reproduce problem and see what I can gather from logs. Backtrace: 0: /usr/bin/X(xf86SigHandler+0x85) [0x80cec63] Fatal server error: Caught signal 11. Server aborting (II) AIGLX: Suspending AIGLX clients for VT switch (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 3 (II) intel(0): xf86UnbindGARTMemory: unbind key 4 from what I gather sig11 is related to "out of boundary" access stuff: """Signal 11, or officially know as "segmentation fault", means that the program accessed a memory location that was not assigned. That's usually a bug in the program. So if you're writing your own program, that's the most likely cause. """ feel free to mark it as a duplicate of bug #253062 - URLs there crash my X11 session in the very same fashion. *** This bug has been marked as a duplicate of bug 253062 *** |