Phillip Jones wrote:
here are the ones that haven't been purged there was another screen full
I purged by mistake.
Only two of those are from SeaMonkey 2.0.3:
http://crash-stats.mozilla.com/report/index/9f52f227-c6ca-42cc-a43f-17d022100314
which is a crash in Flash player, and
http://crash-stats.mozilla.com/report/index/b4006c9f-bbee-4086-8dbd-97d2c2100219
which is a crash in "Foundation", which I guess is an Apple operating
system component.
Both of those are not crashes in SeaMonkey code.
Some of your older crashes have been fixed in SeaMonkey 2.0.x for quite
some time.
We know that we have fixed a number of crash bugs in the various 2.0.x
updates - I don't claim none were there, but we are monitoring the
reports and seeing to getting them fixed. SeaMonkey 2.0.4 should not
have much left in our own code that gives serious crashing pain but if
you encounter any, please make sure you send in the reports and we'll
take a look - esp. if you notify or ask us about those specific ones.
Unfortunately, we can't fix up 3rd-party binary code such as Flash or
Mac OS X, which are unfortunately also much slower in coming up with
various kinds of fixes (Adobe even claims that Flash doesn't have and
practically never had crashes or security issues, even though we have
all kind of evidence to the contrary).
Altogether somewhere over 20. and this doesn't count hangs which don't
report as crashes. Might be in the crash system
No, the crash reporter is not invoked unless SeaMonkey has already
crashed, and the crash reporter is a separate process, you would see that.
The hangs might be something completely different.
Robert Kaiser
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
