Closed Bug 306518 Opened 19 years ago Closed 19 years ago

Crash when viewing ANY local file [@ libgobject-2.0.so.0 + 0x27115]

Categories

(Core :: Widget: Gtk, defect)

1.8 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sgifford, Assigned: blizzard)

Details

(Keywords: crash)

Crash Data

Firefox build 20050827 crashes reliably for me when viewing a particular local
file (which I'll attach shortly).  An example TalkBack is TB8869286Y.
It turns out that trying to upload the file to this bug crashes the browser. 
Note that to see the crash, I have to save this file on my hard drive and view
it with File|Open File.

I've put a copy of the file at:

    http://www.suspectclass.com/~sgifford/mozbug/breaks-mozilla.html
Severity: normal → critical
Keywords: crash
Also, 1.0.6 views the file fine.
This actually crashes when I open *ANY* local file using the file picker.  Works
fine if I type a file: URL in the URLbar instead.  It seems to crash whenever
using the file picker.

This is on Fedora Core 2, kernel 2.6.10, gnome-libs 1.4.1.2, gtk-config 1.2.10.

Component: General → File Handling
Summary: Crash when viewing local file → Crash when viewing ANY local file
Incident ID: 8869286
Stack Signature	libgobject-2.0.so.0 + 0x27115 (0x008fe115) a2a79ac0
Product ID	Firefox15
Build ID	2005082705
Trigger Time	2005-08-30 10:56:38.0
Platform	LinuxIntel
Operating System	Linux 2.6.10-1.12_FC2customsg1
Module	libgobject-2.0.so.0 + (00027115)
URL visited	
User Comments	Viewing local page.
Since Last Crash	0 sec
Total Uptime	3 sec
Trigger Reason	SIGSEGV: Segmentation Fault: (signal 11)
Source File, Line No.	N/A
Stack Trace 	
libgobject-2.0.so.0 + 0x27115 (0x008fe115)
libgobject-2.0.so.0 + 0x1a6b2 (0x008f16b2)
libgtk-x11-2.0.so.0 + 0x1fa2b7 (0x00c4b2b7)
libgtk-x11-2.0.so.0 + 0x1f3af1 (0x00c44af1)
libglib-2.0.so.0 + 0x26ccc (0x0028cccc)
libglib-2.0.so.0 + 0x24252 (0x0028a252)
libglib-2.0.so.0 + 0x25348 (0x0028b348)
libglib-2.0.so.0 + 0x25680 (0x0028b680)
libglib-2.0.so.0 + 0x25cc3 (0x0028bcc3)
libgtk-x11-2.0.so.0 + 0x10f923 (0x00b60923)
nsAppShell::Run() 
[/builds/tinderbox/Fx-Mozilla1.8/Linux_2.4.21-27.0.4.ELsmp_Depend/mozilla/widget/src/gtk2/nsAppShell.cpp,
line 141]
nsAppStartup::Run() 
[/builds/tinderbox/Fx-Mozilla1.8/Linux_2.4.21-27.0.4.ELsmp_Depend/mozilla/toolkit/components/startup/src/nsAppStartup.cpp,
line 146]
XRE_main() 
[/builds/tinderbox/Fx-Mozilla1.8/Linux_2.4.21-27.0.4.ELsmp_Depend/mozilla/toolkit/xre/nsAppRunner.cpp,
line 2324]
main() 
[/builds/tinderbox/Fx-Mozilla1.8/Linux_2.4.21-27.0.4.ELsmp_Depend/mozilla/browser/app/nsBrowserApp.cpp,
line 62]
libc.so.6 + 0x14ad4 (0x004e1ad4)
Assignee: nobody → blizzard
Component: File Handling → Widget: Gtk
Product: Firefox → Core
QA Contact: general → gtk
Summary: Crash when viewing ANY local file → Crash when viewing ANY local file [@ libgobject-2.0.so.0 + 0x27115]
Version: 1.5 Branch → 1.8 Branch
This is a serious dogfood bug for me, and has pushed me back to using stable
builds instead of the branch nightlies.  I can't use the File|Open dialog at
all.  If I forget and try to use it, Firefox crashes and I lose all of my open
pages.
Flags: blocking1.8b5?
there should be a way to disable the gtk2 filepicker (i don't remember how) if 
this is limited to the open dialog.

based on the stack, you'll probably need to get symbols for gtk2 and glib, and 
build mozilla --enable-debugger-info-modules.
This is around 27th on the topcrash list for b1/trunk, but none in about a week,
as far as I can tell.  Scott, can you retest on this?

This sounds a lot like the gtk2.7 filepicker bug that seems to have been fixed
on the gtk2 end.
Thanks mconnor, I downloaded a more recent nightly (20050925) and the bug seems
mostly fixed.  It still crashes sometimes when using the file picker, but
sometimes is better than all the time.  I've filed bug 310137 for the remaining
issues I'm aware of.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Flags: blocking1.8b5?
Crash Signature: [@ libgobject-2.0.so.0 + 0x27115]
You need to log in before you can comment on or make changes to this bug.