Created attachment 362505 [details] The ~/.xsession-errors file Description of problem: Firefox crashes every time when manage bookmarks through mouse clicks. Using the menus do not produce this problem, however. Version-Release number of selected component (if applicable): firefox-3.5.3-1.fc12.i686 xulrunner-1.9.1.3-1.fc12.i686 How reproducible: Every time Steps to Reproduce: 1. Click the star at the right corner of the address bar to add a bookmark of the current url. 2. Click the star again to open the bookmark editor dialog. 3. Click the "Choose..." item from the popup menu of the "folder" combox Actual results: Firefox crashes. Expected results: Let you choose a folder for the current bookmark to be moved into. Additional info:
Can you attach back-trace of the crash?
(In reply to comment #1) > Can you attach back-trace of the crash? I'm so sorry, but help is needed. I'm new to program debug. And just find out how to obtain back-trace. I run the following commands: gdb /usr/lib/firefox-3.5.3/firefox 2>&1 | tee ~/gdb-firefox.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) run and followed the steps to reproduce the bug result, but firefox didn't crash, it hangs, and I can do nothing else. So I tried to kill the terminal process on another tty, and thought I might be able to do the debug on the other tty, but I do not know how to run a program on a particular tty, since firefox is a gui program. I searched the internet, but didn't see any information about this. I'm so sorry about it.
Please install firefox-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install firefox Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. Thanks in advance.
(In reply to comment #3) > Please install firefox-debuginfo (debuginfo-install is from > yum-utils package). > > debuginfo-install firefox > > Then run firefox with a parameter -g. That will start firefox running inside of > gdb debugger. Then use command run and do whatever you did to make firefox > crash. When it happens, you should go back to the gdb and run > > (gdb) thread apply all backtrace > > This produces usually many screens of the text. Copy all of them into a text > editor and attach the file to the bug as an uncompressed attachment. > > Thanks in advance. Maybe you did not understand me. I mean, I now know how to obtain backtrace, but the firefox running from gdb, did not crash, instead, it hangs, and makes the actions to the current tty have no effects, so I have to kill the terminal in another tty, since the firefox and the tty process ID can not be killed. As a result, I can not obtain the backtrace, for the gdb has already forced out without completed. So, I think, I may have to run gdb on another tty without gui, and then start firefox in gdb but put it on the gui tty, then we can act to produce the bug. But, the problem is that, I don't know the method to specify a tty when execute a command through command line. Ask again for help. And thanks for the reply.
If the firefox/debugger/whatever hangs you can attach the debugger directly to it by gdb --pid=xxx where xxx is a PID of the process. And then you can gen the backtrace...
Created attachment 362644 [details] gdb backtrace
(In reply to comment #5) > If the firefox/debugger/whatever hangs you can attach the debugger directly to > it by gdb --pid=xxx where xxx is a PID of the process. And then you can gen the > backtrace... Sorry again, but following your instructions produce nothing. I execute the command gdb --pid=2223, in which 2223 referred to the firefox's PID, and the command thread apply all backtrace produced nothing I tried the command backtrace full it said "No stack" and I tried to point the pid to the gdb that hanged up with firefox, and it generates the result in the attachment. I think it may be useless. And, I have to know how to execute a gui program on a specified tty, so that maybe the tty running firefox hanged up, but I can still use the gdb to get the results, or maybe there are some thing else I don't know. So sorry again.
I wonder why the whole debugging session hangs. Try to run firefox as 'firefox -g" and then try to run it from the debugger (by run gdb command). You should be able to break the debugging session by CTRL+C (from the gdb console).
(In reply to comment #4) > Maybe you did not understand me. I mean, I now know how to obtain backtrace, Are you sure? Nothing against you, but firefox is a strange beast -- running gdb /usr/lib64/firefox*/firefox gives very different results than firefox -g (which is the canonical way how to run firefox inside of gdb)
(In reply to comment #9) > (In reply to comment #4) > > Maybe you did not understand me. I mean, I now know how to obtain backtrace, > > Are you sure? Nothing against you, but firefox is a strange beast -- running > > gdb /usr/lib64/firefox*/firefox > > gives very different results than > > firefox -g > > (which is the canonical way how to run firefox inside of gdb) Really the result is different? Anyhow, actually, I followed the two procedures, but the results are almost the same. And, Firefox on my system is the 32 version.
Created attachment 362677 [details] gdb backtrace
(In reply to comment #1) > Can you attach back-trace of the crash? The backtrace is attached. Finally, I find out the tips about specify a particular tty for a program. And I run the following command from tty2 firefox -g --display :0 2>&1 | tee gdb-firefox.txt (gdb)run and shifted to tty1 to follow the steps to produce the bug results, and turned to tty1, in which I haven't to do CTRL-C, for gdb gave me the prompt, and I run thread apply all backtrace so now, due to the backtrace result. Thanks for your attention.
0x05bcdcbe in ?? () from /usr/lib/libsqlite3.so.0 The crash is inside sqlite (a database engine). Please install sqlite-debuginfo package and try to get the backtrace again (we need symbols from /usr/lib/libsqlite3.so.0)
Created attachment 362683 [details] gdb backtrace
Cool. Moving to sqlite component...
*** Bug 524504 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Needless to say, this needs to be fixed. Meanwhile: For those of us who need to file a bookmark, I found that (a) backup/exporting my bookmarks (b) exiting firefox (c) removing $HOME/.mozilla/firefox/12345678.default/places.sqlite* (d) restarting firefox ...managed to preserve my bookmarks and make the crash go away. The bookmarks must be stored in some alternate form elsewhere, because I never needed to explicitly restore them.
*** Bug 537093 has been marked as a duplicate of this bug. ***
*** Bug 536369 has been marked as a duplicate of this bug. ***
*** Bug 528385 has been marked as a duplicate of this bug. ***
*** Bug 533195 has been marked as a duplicate of this bug. ***
*** Bug 537999 has been marked as a duplicate of this bug. ***
*** Bug 537638 has been marked as a duplicate of this bug. ***
A possible (although sledgehammerish) fix is to update sqlite to 3.6.20 which doesn't seem to have this issue. Test reports welcome, until it becomes available in rawhide you can grab 3.6.20 from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1816182
*** Bug 538793 has been marked as a duplicate of this bug. ***
*** Bug 539934 has been marked as a duplicate of this bug. ***
sqlite-3.6.20-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/sqlite-3.6.20-1.fc12
With sqlite-3.6.20-1.fc12 I can save any url page in any bookmark sub-menu from "Bookmarks Menu". Many thanks!
sqlite-3.6.20-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update sqlite'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12178
*** Bug 540399 has been marked as a duplicate of this bug. ***
*** Bug 540657 has been marked as a duplicate of this bug. ***
*** Bug 540832 has been marked as a duplicate of this bug. ***
*** Bug 539614 has been marked as a duplicate of this bug. ***
*** Bug 541602 has been marked as a duplicate of this bug. ***
*** Bug 541539 has been marked as a duplicate of this bug. ***
*** Bug 541640 has been marked as a duplicate of this bug. ***
*** Bug 541762 has been marked as a duplicate of this bug. ***
*** Bug 542335 has been marked as a duplicate of this bug. ***
*** Bug 542390 has been marked as a duplicate of this bug. ***
*** Bug 542527 has been marked as a duplicate of this bug. ***
*** Bug 543217 has been marked as a duplicate of this bug. ***
*** Bug 543351 has been marked as a duplicate of this bug. ***
sqlite-3.6.20-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 544054 has been marked as a duplicate of this bug. ***
*** Bug 544158 has been marked as a duplicate of this bug. ***
*** Bug 542387 has been marked as a duplicate of this bug. ***
*** Bug 542143 has been marked as a duplicate of this bug. ***
*** Bug 543451 has been marked as a duplicate of this bug. ***
*** Bug 572471 has been marked as a duplicate of this bug. ***