Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Crash Reports from a very crashy Firefox

0 views

Skip to first unread message

Ted Mielczarek

unread,

Jun 29, 2009, 9:48:24 AM6/29/09

to dev-q...@lists.mozilla.org

There's not much rhyme or reason here, except to note that in everything but
the nsCycleCollector::MarkRoots (and the bare address crash), it looks like
null pointer dereferences. (The crash addresses are all very small, probably
an offset from NULL.)

I will note that nsCycleCollector::MarkRoots is in our topcrash list,
currently #9 for Firefox 3.0.11. I will also note that he didn't seem to
think it was Firefox's problem, more that his computer had a problem. Also,
he at one point fell back to IE, only to have that crash on him as well.

Any thoughts?

-Ted

Mike Shaver

unread,

Jun 29, 2009, 9:53:01 AM6/29/09

to Ted Mielczarek, dev-q...@lists.mozilla.org

On Mon, Jun 29, 2009 at 9:48 AM, Ted Mielczarek<t...@mielczarek.org> wrote:
> Any thoughts?

"memtest86" is the first thing that pops into mind when I see that
many different crashes due to invalid memory accesses...

Mike

Anthony Hughes

unread,

Jun 29, 2009, 11:47:16 AM6/29/09

to Ted Mielczarek, dev-q...@lists.mozilla.org, Mike Shaver

Yeah, I would definitely run memtest. My grandfather had a similar issue when 3.0 was released. I tried upgrading him from 2.0 but 3 just kept crashing. His computer specs were pretty low too (P3-800, 256MB SDRAM, Win XP SP2). As it turns out, one of the RAM modules had gone bad (the low system specs didn't help either). For now, his computer is still using Firefox 2 as it is the only browser that doesn't seem to crash all that often.

Cheers,

Anthony Hughes

Mike
_______________________________________________
dev-quality mailing list
dev-q...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-quality

0 new messages