Red Hat Bugzilla – Bug 478340
seamonkey crash on web-pages with cookies
Last modified: 2009-01-13 09:33:01 EST
Created attachment 327897 [details]
output of gecko-bugreport
Description of problem:
seamonkey browser crash on loading web-pages with cookies (spec)
Version-Release number of selected component (if applicable):
run seamonkey and open site http://habrahabr.ru
Steps to Reproduce:
1. run seamonkey
2. open site http://habrahabr.ru
version seamonkey-1.1.14-1.fc9.i386.rpm (on Fedora10) - is not crashed
Thanks for the bug report. We have reviewed the information you have provided above, and unfortunately the attached backtrace is for technical reasons not useful for us, so I have to ask you for providing another one by the old means.
First of all, could we get output of the command
rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*
Please also install firefox-debuginfo (debuginfo-install is from
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.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Can you please check the upcoming F10 update? (seamonkey-1.1.14-2.fc10.i386)
Created attachment 328318 [details]
# rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*
Vladimir, Martin asks if you can install the new updated seamonkey package.
Once you have installed and tried the package version, mentioned in comment 2, can you please report back?
please give me link to this pkg
It's here - https://admin.fedoraproject.org/updates/F10/FEDORA-2009-0217
Doesn't feel like NEW anymore.
pkg seamonkey-1.1.14-2.fc10.i386 dont have this bug
Vladimir, thanks a lot for testing. So it looks like it's the same compiler optimization problem that Martin is already working on. Over to him, I guess this can be marked a duplicate.
okay, closing as duplicate.
*** This bug has been marked as a duplicate of bug 468415 ***