Closed Bug 1918912 Opened 1 year ago Closed 1 year ago

Mozilla Firefox Crashes on Form Submission After Recent Update

Categories

(Core :: DOM: Forms, defect)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sakeban7, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36

Steps to reproduce:

After the latest Firefox update (version [insert version number]), I've encountered a consistent crash issue when submitting forms on various websites. This problem seems to have started occurring right after the update and affects different types of forms, including those on both HTTP and HTTPS sites.

The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Application Update
Product: Firefox → Toolkit

can you go to about:crashes, submit the crash reports and then post the report IDs here.

Flags: needinfo?(sakeban7)

okay.

Flags: needinfo?(sakeban7)

Do reopen if you get round to doing comment 2.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE

hank you for your suggestions. I’ve attempted to troubleshoot the issue by trying the following steps:

Ran Firefox in Safe Mode to rule out add-on interference, but the form submission crash persists.
Cleared the cache and cookies, and ensured I'm using the latest version of Firefox.
However, the issue still occurs when submitting forms. I will follow up with crash reports once available, but in the meantime, I’d appreciate any additional guidance or next steps.

Thank you for your assistance.

:Sakeban crash reports should be visible in about:crashes typed in the the URL bar after the crash, see details here.

Moving to DOM: Forms as this is unlikely to relate to the updater.

Component: Application Update → DOM: Forms
Product: Toolkit → Core
Version: Firefox 117 → unspecified
You need to log in before you can comment on or make changes to this bug.