Launchpad has imported 10 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=653914.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-04-30T13:04:54+00:00 robert wrote: 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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/16 ------------------------------------------------------------------------ On 2011-04-30T13:24:41+00:00 Antoine-mechelynck-gmail wrote: 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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/17 ------------------------------------------------------------------------ On 2011-04-30T13:29:09+00:00 Antoine-mechelynck-gmail wrote: 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). Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/18 ------------------------------------------------------------------------ On 2011-04-30T14:09:43+00:00 robert wrote: (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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/19 ------------------------------------------------------------------------ On 2011-05-01T11:57:37+00:00 Stefan Persson wrote: 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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/23 ------------------------------------------------------------------------ On 2011-05-01T13:29:22+00:00 robert wrote: Okay, disabling spellchecker fixed this problem. I can now open emails without Seamonkey crashing. No problem in Firefox but I prefer Seamonkey . Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/24 ------------------------------------------------------------------------ On 2011-05-01T17:15:24+00:00 Philip-chee wrote: 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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/25 ------------------------------------------------------------------------ On 2011-05-04T15:20:25+00:00 Matti-mversen wrote: *** Bug 654209 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/28 ------------------------------------------------------------------------ On 2011-05-19T20:52:43+00:00 Anders Kaseorg wrote: 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. Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/30 ------------------------------------------------------------------------ On 2011-05-19T21:23:15+00:00 Anders Kaseorg wrote: 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 Reply at: https://bugs.launchpad.net/hunspell/+bug/723830/comments/32 ** Changed in: seamonkey Status: Unknown => Invalid ** Changed in: seamonkey Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/723830 Title: seamonkey-2.0-bin assert failure: *** buffer overflow detected ***: /usr/lib/seamonkey-2.0.11/seamonkey-2.0-bin terminated -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
