Closed Bug 32355 Opened 25 years ago Closed 25 years ago

Crash in GetSharedGC when clicking on link

Categories

(Core :: XUL, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 25155

People

(Reporter: rzach, Assigned: pavlov)

References

()

Details

(Keywords: crash)

To reproduce: 1. Go to http://derstandard.at 2. Click on first article link in the middle frame Actual result: page loads, then Mozilla segfaults Expected result: no crash Stack trace: Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkObject' Gdk-CRITICAL **: file gdkgc.c: line 288 (gdk_gc_unref): assertion `gc != NULL' failed. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1711] Program received signal SIGSEGV, Segmentation fault. 0x4130bfbf in nsToolkit::GetSharedGC () (gdb) where #0 0x4130bfbf in nsToolkit::GetSharedGC () #1 0x4130d72b in nsWidget::GetNativeData () #2 0x41312f57 in nsWindow::GetNativeData () #3 0x413c255b in nsRenderingContextGTK::Init () #4 0x41316fae in nsBaseWidget::GetRenderingContext () #5 0x41311781 in nsWindow::DoPaint () #6 0x41311915 in nsWindow::Update () #7 0x41311659 in nsWindow::UpdateIdle () #8 0x405a4bd9 in g_idle_dispatch () #9 0x405a3be6 in g_main_dispatch () #10 0x405a41a1 in g_main_iterate () #11 0x405a4341 in g_main_run () #12 0x404c9859 in gtk_main () #13 0x413007da in nsAppShell::Run () #14 0x40f5bcf2 in NSGetModule () #15 0x804af9c in JS_PushArguments () #16 0x804b2bc in JS_PushArguments () #17 0x402eccb3 in __libc_start_main (main=0x804b130 <JS_PushArguments+7344>, argc=1, argv=0xbffff824, init=0x8049190 <_init>, fini=0x804c0a0 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff81c) at ../sysdeps/generic/libc-start.c:78 Guessing XP Toolkit; pavlov. Linux build 2000.03.17.09
Keywords: crash
That's the same stack trace as bug #31791
dup of the bug that one is duped on *** This bug has been marked as a duplicate of 25155 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified duplicate.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.