Philip Chee wrote:
On Wed, 24 Nov 2010 14:38:07 -0600, Rufus wrote:
Went two days with no crashes, this time I had multiple crashes using
two different Profiles - most on restart/start attempts; both in the
same Profile and on switching Profiles. Also tried deleting the
residual sessiostore.json file before restart - CRASH.
Report ID Date Submitted
bp-1a14ddeb-e6cf-457d-a792-b84042101124 11/24/10 2:31 PM
No crash stack.
bp-5cd20ffa-5772-4b9a-bc48-533c22101124 11/24/10 2:29 PM
bp-ec60a3af-1376-45af-ba7d-916612101124 11/24/10 2:29 PM
bp-25694e45-f1d4-405f-8951-957982101124 11/24/10 2:28 PM
bp-9d437461-1022-4e1a-9a33-617a32101124 11/24/10 2:28 PM
http://crash-stats.mozilla.com/report/index/bp-5cd20ffa-5772-4b9a-bc48-533c22101124
http://crash-stats.mozilla.com/report/index/bp-ec60a3af-1376-45af-ba7d-916612101124
http://crash-stats.mozilla.com/report/index/bp-25694e45-f1d4-405f-8951-957982101124
http://crash-stats.mozilla.com/report/index/bp-9d437461-1022-4e1a-9a33-617a32101124
All crashing with this crash signature:
NS_GetBrightness(unsigned char, unsigned char, unsigned char)
I can't find a bug with this crash signature. Might be worth filing a bug.
0 seamonkey-bin NS_GetBrightness
layout/base/nsCSSColorUtils.cpp:147
Please File a bug in:
Product: Core.
Component: Layout.
Version 1.9.1.
With the summary something like:
crash [...@ns_getbrightness(unsigned char, unsigned char, unsigned char)]
Phil
WILCO - at least it looks like you were able to find something I never
would have. I'll let you know the bug ID once I submit.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
