Closed Bug 1847115 Opened 1 year ago Closed 1 year ago

Crash in [@ java.lang.NoSuchMethodError: at mozilla.components.browser.engine.gecko.GeckoNimbus$Features$pdfjs$2.invoke(GeckoNimbus.kt:9)]

Categories

(GeckoView :: PDF Viewer, defect, P3)

Unspecified
Android
defect

Tracking

(firefox116 affected, firefox117 ?, firefox118 ?)

RESOLVED WORKSFORME
Tracking Status
firefox116 --- affected
firefox117 --- ?
firefox118 --- ?

People

(Reporter: cpeterson, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/7a589994-6000-4ce8-8c6f-f52030230803

Is this a PDF Viewer bug or a Nimbus bug? This crash signature first appeared in 116. So far, all (22) crash reports are from one user.

Java stack trace:

java.lang.NoSuchMethodError: No direct method <init>(Ljava/lang/String;Lkotlin/jvm/functions/Function0;Lkotlin/jvm/functions/Function1;)V in class Lorg/mozilla/experiments/nimbus/internal/FeatureHolder; or its super classes (declaration of 'org.mozilla.experiments.nimbus.internal.FeatureHolder' appears in /data/app/org.mozilla.firefox-Q1MCE5tRUsczC-L9FrcfaA==/base.apk!classes2.dex)
	at mozilla.components.browser.engine.gecko.GeckoNimbus$Features$pdfjs$2.invoke(GeckoNimbus.kt:9)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:21)
	at org.mozilla.fenix.nimbus.FxNimbus.reinitialize(FxNimbus.kt:5)
	at org.mozilla.fenix.nimbus.FxNimbus.<clinit>(FxNimbus.kt:19)
	at org.mozilla.fenix.utils.Settings.getMr2022Sections(Settings.kt:1)
	at org.mozilla.fenix.utils.Settings.getEnabledTotalCookieProtection(Settings.kt:1)
	at org.mozilla.fenix.utils.Settings.<init>(Settings.kt:1136)
	at org.mozilla.fenix.components.Components$settings$2.invoke(Components.kt:7)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:21)
	at org.mozilla.fenix.components.Components.getSettings(Components.kt:3)
	at org.mozilla.fenix.ext.ContextKt.settings(Context.kt:10)
	at org.mozilla.fenix.components.Analytics$experiments$2.invoke(Analytics.kt:12)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:21)
	at org.mozilla.fenix.components.Analytics.getExperiments(Analytics.kt:3)
	at org.mozilla.fenix.FenixApplication.initialize(FenixApplication.kt:116)
	at org.mozilla.fenix.FenixApplication.onCreate(FenixApplication.kt:4)
	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1127)
	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6097)
	at android.app.ActivityThread.-wrap1(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1791)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:7000)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

That is interesting, I'm not sure what the root cause is, but I have some background. PDF.js is calling Nimbus to get information from an experiment through onGetNimbusFeature. It reads to me like the GeckoNimbus was a different version that didn't have a function it needed or something like that? These Nimbus functions were specially added around the same time for the PDF use case.

TheonGetNimbusFeature API is going to be swapped out to a new ExperimentDelegate in bug 1840658 too (hopefully in 118), so the PDF will be calling to Nimbus differently soon.

See Also: → 1833093, 1840658
Severity: -- → S4
Priority: -- → P3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.