Comment 9 for bug 723830

I find the same (or similar) defect in 2.0.13. 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. Since the Ubuntu-based .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.

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. 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. 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.

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. If not the kernel, what about changes to the X server?