739576 - Crash ending in "couldn't rename minidump file"

Status: RESOLVED DUPLICATE of bug 738168

(Firefox for Android Graveyard :: General, defect)

Description

[Cristian Nicolae (:xti)]

This bug was filed from the Socorro interface and is 
report bp-bec33837-47af-446c-a4f5-361212120327 .
============================================================= 

This crash occurred just after I opened Fennec. 

--
Firefox 14.0a1 (2012-03-27)
Device: Samsung Galaxy S
OS: Android 2.2

Comment 1

[Cristian Nicolae (:xti)]

Attachment: crash log

Comment 2

[Scoobidiver (away)]

This crash signature is not a valid one.

Comment 3

[Cristian Nicolae (:xti)]

(In reply to Scoobidiver from comment #2)
> This crash signature is not a valid one.

That's all I have. I hope that the crash log to be more useful than the crash signature.

Comment 4

[Brad Lassey [:blassey] (use needinfo?)]

that log shows why we don't have a signature (dump file wasn't found) but not why we crashed

E/GeckoCrashReporter( 3240): java.io.FileNotFoundException: /data/data/org.mozilla.fennec/files/mozilla/2egu5dz5.default/minidumps/19c1faf7-4007-2eb4-3c49da37-0d9f56db.dmp (No such file or directory)

Comment 5

[Martijn Wargers (dead)]

I guess this bug might as well be closed->incomplete, since at this point there is no information whatsoever to what caused the crash.

Comment 6

[Cristian Nicolae (:xti)]

(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #5)
> I guess this bug might as well be closed->incomplete, since at this point
> there is no information whatsoever to what caused the crash.

It occurs again today on the latest Nightly build (03/28).

Comment 7

[Scoobidiver (away)]

(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #5)
> I guess this bug might as well be closed->incomplete, since at this point
> there is no information whatsoever to what caused the crash.
Can we at least investigate why the minidump hasn't been renamed? Is the phone memory full?

Comment 8

[Cristian Nicolae (:xti)]

(In reply to Scoobidiver from comment #7)

> Can we at least investigate why the minidump hasn't been renamed? Is the
> phone memory full?

No, there is enough free internal memory for my device, about 1,6 Gb. Also the free RAM is about 127 Mb before running Fennec, so it should be something else than a memory issue.

Comment 9

[Martijn Wargers (dead)]

Cristian, are you still seeing this crash and you still get the "couldn't rename minidump file" thing?

Comment 10

[(not currently active) Ted Mielczarek]

The underlying crashreporter problem sounds very similar to bug 738168.

Comment 11

[Cristian Nicolae (:xti)]

(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #9)
> Cristian, are you still seeing this crash and you still get the "couldn't
> rename minidump file" thing?

I cannot reproduce this crash on the latest Nightly. Perhaps we could close it as WFM and I will reopen it if will occur again. This crash is a little bit different than others.

--
Firefox 14.0a1 (2012-04-17)
Device: Samsung Galaxy S (Captivate)
OS: Android 2.2

Comment 12

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I think this is a dup of bug 738168.

Comment 13

[Cristian Nicolae (:xti)]

(In reply to Naoki Hirata :nhirata from comment #12)
> I think this is a dup of bug 738168.
> 
> *** This bug has been marked as a duplicate of bug 738168 ***

Fennec was not running from SD Card when this crash occurred. I will try to reproduce it again after bug 738168 will be fixed