Closed Bug 206170 Opened 21 years ago Closed 21 years ago

Browser crashes with URL supplied on Linux with gtk2

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 180309

People

(Reporter: Mitch, Assigned: blizzard)

References

()

Details

(Keywords: crash)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030516
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030516

Browser crashes with URL provided. Please don't report WFM on WIndows/Solaris.
This appears to be a gtk2 Linux issue. Probably related to bug 205492

If someone has a debug build of mozilla with gtk2 maybe we can get a good stack ?

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.wincustomize.com/index.asp?Cmd=full&NewsID=1510
2.
3.

Actual Results:  
Browser crashes

Expected Results:  
Obvious
.
Assignee: general → blizzard
Severity: major → critical
Keywords: crash
what build are you using?  (self-built, RPM, etc)
if you start Mozilla froma terminal, does it print any messages before crashing?
In response to Andrew: Self built mozilla. No console error messages frmo cli
startup. Stripped stack as follows. I will rebuild a debugging version and attack 
a better stack soon.


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 28370)]
0x40bd578b in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
(gdb) bt
#0  0x40bd578b in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#1  0x40bd5951 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#2  0x40bd59ca in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#3  0x40bb5a2a in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#4  0x40bacc88 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#5  0x40bbc205 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#6  0x40c7f853 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
..repeats for 40 more stack frames...
#46 0x40bf8ab6 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#47 0x40c073a9 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#48 0x40c06ec7 in NSGetModule () from /usr/local/mozilla/components/libgklayout.so
#49 0x40925fc8 in PL_HandleEvent () from /usr/local/mozilla/libxpcom.so
#50 0x40925eaf in PL_ProcessPendingEvents () from /usr/local/mozilla/libxpcom.so
#51 0x40927114 in nsEventQueueImpl::ProcessPendingEvents ()
   from /usr/local/mozilla/libxpcom.so
#52 0x4126d5fc in nsIProperties::GetIID ()
   from /usr/local/mozilla/components/libwidget_gtk2.so
#53 0x4047355e in g_io_unix_dispatch () from /usr/local/lib/libglib-2.0.so.0
#54 0x40453b7b in g_main_dispatch () from /usr/local/lib/libglib-2.0.so.0
#55 0x404549ca in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0
#56 0x40454da7 in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.0
#57 0x404554c0 in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.0
#58 0x401a9dc1 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.0
#59 0x4126d8e9 in nsAppShell::Run () from
/usr/local/mozilla/components/libwidget_gtk2.so
#60 0x4123d7ff in NSGetModule () from /usr/local/mozilla/components/libnsappshell.so
#61 0x08055c8d in nsGetServiceByContractID::operator() ()
#62 0x08054572 in main ()
#63 0x405f556d in __libc_start_main () from /lib/libc.so.6
(gdb) quit
The program is running.  Exit anyway? (y or n) y
Oh, and build is as reported above in the "Build Identifier:" at the top of this
bug description.
do you have any MS .fon fonts in your font path (bug 180309)?
Attached file Stack from crash
Nope, no .fon files in my font path, but my stack (attached) does look like
comment #39 of the aforementioned bug

http://bugzilla.mozilla.org/show_bug.cgi?id=180309#c39

Looks like a dup to me..
This does appear to be a font issue as Andrew indicated in comment #5.
Cleared my font path and all is fine now.

Closing as a dup.

*** This bug has been marked as a duplicate of 180309 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: