Chris Ilias wrote:
On 10-11-27 9:54 AM, Ray_Net wrote:
Chris Ilias wrote:
Your crash signature is:
GetAdvanceForGlyphs
There is a bug report for that at
<https://bugzilla.mozilla.org/show_bug.cgi?id=489691>, but it was fixed
5 months before SeaMonkey 2.0 was released.
Does the crash always occur when composing a message?
The already posted bug "resolved" speak about x86 Mac OSX FireFox
Unknown crash ID (error not really the same)
And mine is Windows XP SP3 SeaMonkey with the crash ID
"bp-8ee1cb47-0e72-45c3-a70e-898c02101124" giving error
"EXCEPTION_ACCESS_VIOLATION_READ"
This looks NOT the same problem ...
I don't know, but it has the same crash signature. The "Crash Reason" is
not really indicative of the cause. It's like citing "couldn't access a
needed file".
For instance, if you go to <http://crash-stats.mozilla.com/>, and click
on any of the top crashers (which are identified by signature), you'll
see the same reason for many signatures.
Going back to my question, does the crash always occur when composing a
message? I'm not sure I got an answer to that.
I had answered: "I just had this once ... " but not in the same reply.
May be, with only one occurence, it's not interesting to pursue ...
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
