Closed Bug 1811183 Opened 8 months ago Closed 8 months ago

Crash in [@ java.lang.NumberFormatException: at jdk.internal.math.FloatingDecimal.readJavaFormatString(] for input string "any"


(Fenix :: Browser Engine, defect, P2)



(firefox109 wontfix, firefox110+ verified, firefox111 verified)

111 Branch
Tracking Status
firefox109 --- wontfix
firefox110 + verified
firefox111 --- verified


(Reporter: cpeterson, Assigned: aputanu)




(Keywords: crash, regression, Whiteboard: [fxdroid])

Crash Data


(2 files)

@ Roger, this crash looks like a regression in Fenix 106 from the fix for bug 1790425 ( The earliest version with a NumberFormatException: For input string: "any" crash report is 106.0b1 and the fix for bug 1790425 was uplifted to Beta 106.

GeckoPromptDelegate.onDateTimePrompt Bug 1790425's crashes had NumberFormatException: empty String. This bug's crashes have NumberFormatException: For input string: "any".

Crash report:

Java stack trace:

java.lang.NumberFormatException: For input string: "any"
	at jdk.internal.math.FloatingDecimal.readJavaFormatString(
	at jdk.internal.math.FloatingDecimal.parseFloat(
	at java.lang.Float.parseFloat(
	at mozilla.components.browser.engine.gecko.prompt.GeckoPromptDelegate.onDateTimePrompt(GeckoPromptDelegate.kt:117)
	at org.mozilla.geckoview.PromptController$DateTimeHandler.callDelegate(
	at org.mozilla.geckoview.PromptController$DateTimeHandler.callDelegate(
	at org.mozilla.geckoview.PromptController.getResponse(
	at org.mozilla.geckoview.PromptController.handleEvent(
	at org.mozilla.geckoview.GeckoSession$Listener.handleMessage(
	at org.mozilla.gecko.EventDispatcher$
	at android.os.Handler.handleCallback(
	at android.os.Handler.dispatchMessage(
	at android.os.Looper.loopOnce(
	at android.os.Looper.loop(
	at java.lang.reflect.Method.invoke(Native Method)
Flags: needinfo?(royang)

Moving from GeckoView to Fenix because this is an A-C bug.

Component: General → Browser Engine
Priority: -- → P2
Product: GeckoView → Fenix
Whiteboard: [fxdroid]

Looks like the same crash. Adding Alexandru to confirm if there's a corner case that can still cause a crash.

Flags: needinfo?(royang) → needinfo?(aputanu)

Found that any string input set as step is directly passed with the DateTimePrompt. I'll work on a patch to handle this in A-C.

Assignee: nobody → aputanu
Flags: needinfo?(aputanu)

Landed on main:

Crash volume on Release doesn't seem high enough to worry about an uplift to 109, but we will probably want to backport this to v110 still given that it's a small fix w/ an automated test.

Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Flags: qe-verify+

Managed to reproduce the crash in earlier builds:

  • latest RC 109.1.1.
  • latest Beta 110.0b4.
    Verified as fixed on the latest Nightly 111.0a1 (2023-01-27) build by tapping on any item from
    Device used: Oppo Find X5 (Android 12).
Flags: qe-verify+

Alexandru, do you think your crash fix is safe to uplift to Beta 110?

Flags: needinfo?(aputanu)

I think the fix is small enough and safe to uplift to Beta 110, I'll prepare the uplift.

Flags: needinfo?(aputanu)

(In reply to Alexandru Putanu [:aputanu] from comment #10)

Backported to 110

FYI, CI is failing on this push

(In reply to Pascal Chevrel:pascalc from comment #11)

(In reply to Alexandru Putanu [:aputanu] from comment #10)

Backported to 110

FYI, CI is failing on this push

Pascal, where can we find the CI error? Should we revert this fix from Beta 110?

Flags: needinfo?(pascalc)
Flags: needinfo?(aputanu)

As far as I can tell, it was an intermittent issue. Later commits are green.

Flags: needinfo?(pascalc)
Flags: needinfo?(aputanu)

Verified as fixed on the latest Beta 110.0b6 build by tapping on any item from
Device used: Google Pixel 7 (Android 13).
Marking as verified for 110.

You need to log in before you can comment on or make changes to this bug.