Closed
Bug 653914
Opened 14 years ago
Closed 14 years ago
seamonkey crashes whenever I click on mail in gmail.This occurs in safe mode also.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: stanoly30, Unassigned)
References
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
As above. Crashes always and only when trying to open an email in gmail. Firefox does not crash with same operation.
Reproducible: Always
Steps to Reproduce:
1.Start up seamonkey
2.Home page is gmail
3.Click on any email entry
Actual Results:
Total crash. Must restart each time.
Expected Results:
Crash. Must restart.
Not crashed but opened email.
Comment 1•14 years ago
|
||
Did the Crash Reporter pop up, and did you tell it to send a report to Mozilla?
If the answers to both questions are yes, please browse to about:crashes then find (by its date) the line corresponding to this particular crash and paste the crash ID (a string of letters, digits and dashes, probably starting with bp-) into a comment in this bug.
Comment 2•14 years ago
|
||
Oh, and BTW, which version of SeaMonkey were you using at the time of the crash? The answer is similar, but slightly different, to the "Build Identifier" in comment #0, and can be found at the bottom of the page which comes up in response to the "Help → About SeaMonkey" menu item (after resetting the User-Agent to its default if you use the UserAgent Switcher extension).
(In reply to comment #1)
> Did the Crash Reporter pop up, and did you tell it to send a report to Mozilla?
>
> If the answers to both questions are yes, please browse to about:crashes then
> find (by its date) the line corresponding to this particular crash and paste
> the crash ID (a string of letters, digits and dashes, probably starting with
> bp-) into a comment in this bug.
No Crash Reported popped up and about:crashes yields no valid url found.
I am using version seamonkey 2.0.13. I just upgraded Ubuntu to newest 2.6.38-8 kernel.
Version: unspecified → SeaMonkey 2.0 Branch
Comment 4•14 years ago
|
||
Probably this bug:
https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/723830
If you use the latest stable Ubuntu release (Natty Narwhal/11.04), Seamonkey crashes whenever attempting to access the spellchecker. This appears to be a bug in Ubuntu and not in Seamonkey. See the Ubuntu bug page for more information.
Okay, disabling spellchecker fixed this problem. I can now open emails without Seamonkey crashing. No problem in Firefox but I prefer Seamonkey .
Comment 6•14 years ago
|
||
Invalid => Downstream problem. Probably Ubuntu are shipping a newer version of the Hunspell libraries which SeaMonkey 2.0.x isn't designed to work with.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Comment 8•14 years ago
|
||
This isn’t a downstream problem. I think this is fixed by http://hg.mozilla.org/releases/mozilla-2.0/rev/c5b3d7beca8c#l17.29 . The problem was that struct hentry ended with a single char that was used as a variable-length array, and writing multiple chars into the space allocated for a single char triggered fortify checks (even though there was enough space after the end of the struct). Now it ends with a char[1], which fortify recognizes as represending a flexible array.
Comment 9•14 years ago
|
||
For reference, here’s the original hunspell patch:
http://sourceforge.net/support/tracker.php?aid=2812045
and another possibly relevant patch from a comment on LP #723830:
http://sourceforge.net/support/tracker.php?aid=3304798
See Also: → https://launchpad.net/bugs/723830
Comment 10•14 years ago
|
||
OK then, an *upstream* problem (Hunspell)
You need to log in
before you can comment on or make changes to this bug.
Description
•