Closed Bug 1508212 Opened 1 year ago Closed 3 months ago

Crash in java.lang.NullPointerException: at android.view.ViewRootImpl.performDraw(ViewRootImpl.java)

Categories

(Firefox for Android :: General, defect, P2, critical)

Unspecified
Android
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox65 --- wontfix
firefox66 --- fix-optional
firefox67 --- fix-optional

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is
report bp-286ec7b3-4618-4dc1-ba03-668270181119.
=============================================================

Java stack trace:

java.lang.NullPointerException
	at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2680)
	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2256)
	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1295)
	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6400)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:876)
	at android.view.Choreographer.doCallbacks(Choreographer.java:688)
	at android.view.Choreographer.doFrame(Choreographer.java:623)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:862)
	at android.os.Handler.handleCallback(Handler.java:754)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:163)
	at android.app.ActivityThread.main(ActivityThread.java:6221)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794)

This is happening outside of our code so it's unclear to me if it's our fault. Still it's fairly high volume so it's better to track it.

Still pretty high volume on release.

Keywords: regression
Priority: -- → P2

Stefan, who could possibly look into this? Still pretty high volume on release and reports on 67 too.

Flags: needinfo?(sarentz)

No crashes on 67 beta but still high volume on release, marking as fix optional for 67, I guess we'll know if it was fixed for real when 67 ships to release.

The crash ratio on 68.1.1 is too low to address.

Status: NEW → RESOLVED
Closed: 3 months ago
Flags: needinfo?(sarentz)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.