740334 - java.lang.OutOfMemoryError: (Heap Size=32647KB, Allocated=29945KB, Bitmap Size=168KB) at org.json.simple.parser.Yylex.<init>(Yylex.java)

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect, P3)

Description

[Scoobidiver (away)]

There's one crash in 14.0a1/20120328115435: bp-f89def09-7734-469d-bb2d-dbd502120329.

java.lang.OutOfMemoryError: (Heap Size=32647KB, Allocated=29945KB, Bitmap Size=168KB)
	at org.json.simple.parser.Yylex.<init>(Yylex.java:231)
	at org.json.simple.parser.JSONParser.<init>(JSONParser.java:34)
	at org.mozilla.gecko.sync.repositories.android.RepoUtils.getJSONArrayFromCursor(RepoUtils.java:106)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserBookmarksRepositorySession.bookmarkFromMirrorCursor(AndroidBrowserBookmarksRepositorySession.java:875)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserBookmarksRepositorySession.retrieveRecord(AndroidBrowserBookmarksRepositorySession.java:421)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserBookmarksRepositorySession.retrieveDuringStore(AndroidBrowserBookmarksRepositorySession.java:363)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserRepositorySession.createRecordToGuidMap(AndroidBrowserRepositorySession.java:618)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserRepositorySession.putRecordToGuidMap(AndroidBrowserRepositorySession.java:639)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserRepositorySession.updateBookkeeping(AndroidBrowserRepositorySession.java:648)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserBookmarksRepositorySession.updateBookkeeping(AndroidBrowserBookmarksRepositorySession.java:648)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserRepositorySession.replace(AndroidBrowserRepositorySession.java:524)
	at org.mozilla.gecko.sync.repositories.android.AndroidBrowserRepositorySession$1.run(AndroidBrowserRepositorySession.java:469)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
	at java.lang.Thread.run(Thread.java:1027)

More reports at:
https://crash-stats.mozilla.com/report/list?signature=java.lang.OutOfMemoryError%3A+%28Heap+Size%3D32647KB%2C+Allocated%3D29945KB%2C+Bitmap+Size%3D168KB%29+at+org.json.simple.parser.Yylex.%3Cinit%3E%28Yylex.java%29

Comment 1

[Richard Newman [:rnewman]]

Syncing uses memory. OOM doesn't count as crashing IMO.

Comment 2

[Scoobidiver (away)]

(In reply to Richard Newman [:rnewman] from comment #1)
> Syncing uses memory. OOM doesn't count as crashing IMO.
It's not a logcat, it's a crash report. So even if OOM is hard to avoid, it's still a crash.

Comment 3

[Richard Newman [:rnewman]]

(In reply to Scoobidiver from comment #2)
> (In reply to Richard Newman [:rnewman] from comment #1)
> > Syncing uses memory. OOM doesn't count as crashing IMO.
> It's not a logcat, it's a crash report. So even if OOM is hard to avoid,
> it's still a crash.

Do we have any way of distinguishing crashes that are unavoidable and out of our control? Is the right solution from a crash-tracking perspective to mark as WONTFIX or WORKSFORME (which I've done in the past)?

Comment 4

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.