Mozilla Crash Reporter for 64 bit

[Ralf Mardorf]

On Tue, 30 Dec 2014 07:36:47 +1000, Phil wrote:
> Perhaps Firefox is not the problem after all, I'll take your advice 
> David and test the memory.

As I already pointed out earlier, including a link how to do it, a
strace will show you and it's not hard to do.

https://lists.ubuntu.com/archives/kubuntu-users/2014-December/060203.html

A memory test in this case is wrong troubleshooting. Nothing indicates
a bad memory. Evidence suggests that the RAM is ok.

Is there a reason to ignore how troubleshooting is done correctly and
instead to insist in doing things that never ever will show what's
happening?

The earlier post (link above) also explains how to do debugging using
gdb. The messages of gdb at least are useful when filing a bug report.
There's a reason why Ubuntu provides dbg packages.

JFTR the important strace output often is understandable even for new
users.

Since other apps are stable and Firefox already crashes, without much
load, less opened tabs, what exactly leads to a defect RAM?