usr/lib/ seamonkey- 2.0.13/ components/ libgklayout. so(JS_EvaluateU CScriptForPrinc ipals+0x99) usr/lib/ seamonkey- 2.0.13/ components/ libxpconnect. usr/lib/ seamonkey- 2.0.13/ components/ libspellchecker. usr/lib/ seamonkey- 2.0.13/ components/ libcomposer. *** buffer overflow detected ***: /usr/lib/ seamonkey- 2.0.13/ seamonkey- 2.0-bin terminated If not the kernel, what about changes to the X server?Ī similar thing happens each time when I click Create new mail in Yahoo mail! It is very urgent. If the stack traces don't provide enough information, think about my comments and see if they cause you to examine areas of the code that may somehow interact with core components of the environment. I had been using the 2.0.11 release on the 10.10 release of Kubuntu and Ubuntu just prior to this, and did not see any instability whatsoever, so this buffer overflow seems somehow related to infrastructure changes in the 11.04 release stream, but I don't have the tools or the wherewithal to test that conjecture, but it has been my consistent observation. It's too bad we haven't found the root cause of this problem it is really the only defect I've discovered in the 11.04 release cycle, which makes me wonder if there isn't some kind of interaction with the kernels being used. You can close this issue if you wish, but only if you keep another defect open for the same issue for the 2.0.13 build. deb packages are the only variable I can discern, I continue to believe that something in the way you build these packages contributes to the buffer overflow condition. On one hand, the argument might be that I have multiple configurations and that creates problems, but the counter argument to that is that if I download my own instance of Seamonkey (which I did with 2.0.11 and 2.0.13) I do not have this buffer overflow problem, nor do I see it at all if I run it on a non-Canonical distribution. I find the same (or similar) defect in 2.0.13. UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare Title: seamonkey-2.0-bin assert failure: *** buffer overflow detected ***: /usr/lib/ seamonkey- 2.0.11/ seamonkey- 2.0-bin terminated ProcCmdline: /usr/lib/ seamonkey- 2.0.11/ seamonkey- 2.0-bin InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcVersionSign ature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5ĪssertionMessage: *** buffer overflow detected ***: /usr/lib/ seamonkey- 2.0.11/ seamonkey- 2.0-bin terminatedĮxecutablePath: /usr/lib/ seamonkey- 2.0.11/ seamonkey- 2.0-bin Package: seamonkey-browser 2.0.11+ build1+ nobinonly- 0ubuntu2 Until the debugger came up, I had no diagnostic information to provide otherwise I would have sent it in much sooner. Looks like a buffer overflow is the culprit. Previous versions of Seamonkey with Kubuntu or Xubuntu were quite reliable since Alpha testing, even accessing a few Web pages has been difficult. Seamonkey has consistently crashed since I started using the Alpha builds in the 11.04 series.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |