NoOp wrote:
Now if I could stop the SeaMonkey Crashes I'd be happy:
>>
>> Since 10/29/2009 I've had ten Crashes. And I've actually had two or
>> three others That I cleared out before this.
>>
>> In the entire history of SM 1.x including crashes caused by the full
>> circle crash reporter I had maybe 6 (in about 5-6 years). And I used
>> almost as many as many extensions and themes as I use now. Most are
>> triggered during reading email/news.
> Incidentally they have the same Reason for crash:
>
> EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE
>
It's probably crashing due to lack of trimming in your posts...
Note: this post purposely left off trimming& no electrons were killed
in the process. However this might be of use:
http://www.mozilla.org/community/etiquette.html
<quote>
Trim your follow-ups.
Do not quote the entire content of the message to which you are
replying. Include only as much as is necessary for context. Remember
that if someone wants to read the original message, they can; it is
easily accessible. A good rule of thumb is, don't include more quoted
text than new text.
There is always a need for some trimming - either a salutation, a
signature, some blank lines or whatever. If you are doing no trimming
whatsoever of the quoted text, then you aren't trimming enough.
</quote>
Actually the shorter post are more likely to cause the crash.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net http://www.vpea.org
mailto:[email protected]
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
