Closed
Bug 470438
Opened 17 years ago
Closed 17 years ago
Crash if bookmarks are sorted manually
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: rajeev_v_pillai, Unassigned)
Details
(Keywords: crash)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Firefox 3.0.5 exits if after a bookmark has been added, you try to move the
bookmark entry up by dragging it after clicking on "Bookmarks". The same
behaviour results if you try to do the same thing via "Bookmarks > Organize Bookmarks".
Reproducible: Always
Steps to Reproduce:
1. Add a new bookmark
2. Select Bookmarks menu
3. Select and drag (move up) the new bookmark add at the end.
Actual Results:
Firefox exits
Expected Results:
Bookmark entry should be moved.
Comment 1•17 years ago
|
||
Can you try this in safe mode http://support.mozilla.com/en-US/kb/Safe+Mode . Also please follow the directions at https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_WinDbg .
| Reporter | ||
Comment 2•17 years ago
|
||
Tried running in safe-mode:
/opt/gconf/bin/dbus-launch firefox -safe-mode but, the crash-reporter does not
submit the crash report. From tcpdump, I can see that it connects to the crash
reporting server, but, it does not seem to send anything. Crash-reporter just
sits there doing nothing.
I can't use WinDdb as I'm on Linux.
Comment 3•17 years ago
|
||
I understand that you are experiencing a crash. Could you please follow the steps found at http://new.quality.mozilla.org/bug-writing-guidelines, which will help us pinpoint the cause and nature of the crash. The link Natch gave you does not have the Linux info, but this one, https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report does.
@Natch, it is usually better to give this link for crash, as it links to the WinDbg page, and has stuff for mac and Linux users as well.
| Reporter | ||
Comment 4•17 years ago
|
||
| Reporter | ||
Comment 5•17 years ago
|
||
Well, The bug is still present with a clean run of firefox:
$ rm -rf ~/.mozilla
$ /opt/firefox/firefox -safe-mode
### Disable everything and restart as prompted ###
Add a couple of bookmarks
Try sorting the bookmarks by dragging them.
Firefox crashes.
Since crashreporter isn't working for me, I ran firefox under gdb.
The attachment (Comment #4) contains a typescript of the session.
The next attachment contains (Comment #6) a pmap `pidof firefox-bin` output.
Looks like there is a SEGV in gdk_pixbuf_fill().
FYI:
X: xorg-7.4
ATK: 1.24.0
cairo: 1.8.6
glib: 2.18.3
gtk+: 2.14.6 (can this be the cause?)
pango: 1.22.4
pixman: 0.13.2
Hope this helps.
| Reporter | ||
Comment 6•17 years ago
|
||
| Reporter | ||
Updated•17 years ago
|
Attachment #353931 -
Attachment mime type: application/octet-stream → text/plain
| Reporter | ||
Comment 7•17 years ago
|
||
Firefox-3.1b2 does not show the bug.
| Reporter | ||
Comment 8•17 years ago
|
||
Firefox-3.0.4 also has the bug.
Comment 9•17 years ago
|
||
windbg from comment #1 is useless because this is linux, the crashreporter doesn't work if you don't use an official Mozilla.org build but the URL for the crashreporter contains a a little bit for GDB under Linux.
Basically you need debug symbols installed and run it in under GDB to get a full stack trace.
| Reporter | ||
Comment 10•17 years ago
|
||
I did use the official Firefox-3.{0.{5,4},1b2} for the tests.
Comment 11•17 years ago
|
||
Comment on attachment 353930 [details]
Typescript of Firefox-3.0.5 (Linux) running under gdb
um. go install debugging symbols for at least gdk/gdk_pixbuf. but you're going to also need them for firefox.
Comment 12•17 years ago
|
||
you can't debug our binaries (except on windows).
go build your own.
| Reporter | ||
Comment 13•17 years ago
|
||
Using GTK-2.14.7 fixes the problem.
Comment 14•17 years ago
|
||
(In reply to comment #13)
> Using GTK-2.14.7 fixes the problem.
Sounds like a bug in GTK then that caused this, so this bug is INVALID or WORKSFORME :/
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•