Firefox crashes on wordle.net/create if you enter form data and click "go"

RESOLVED WORKSFORME

Status

()

Firefox
Untriaged
--
critical
RESOLVED WORKSFORME
5 years ago
5 years ago

People

(Reporter: Marino, Unassigned)

Tracking

({crash})

16 Branch
x86_64
Windows 7
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

Visted http://www.wordle.net/create, pasted a column of words into the form, clicked "go".

This is exactly what I pasted in: 

sustainables
open~source
authentic~business
design~excellence
choice
transparency
local
openables


Actual results:

The Firefox browser simply vanished without warning. 


Expected results:

The website should've produced a wordle using the column of words I put in.

Comment 1

5 years ago
Is your Java plugin up-to-date (see https://www.mozilla.org/plugincheck/)?
Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?
Can you provide the crash ID from about:crashes if there is some?
Severity: normal → critical
Flags: needinfo?(kilowit)
Keywords: crash

Comment 2

5 years ago
Is your Java plugin up-to-date (see https://www.mozilla.org/plugincheck/)?
Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?
Can you provide the crash ID from about:crashes if there is some?
(Reporter)

Comment 3

5 years ago
(In reply to Scoobidiver from comment #2)
> Is your Java plugin up-to-date (see https://www.mozilla.org/plugincheck/)?
> Does it happen in Safe Mode (see
> https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?
> Can you provide the crash ID from about:crashes if there is some?

Thank you, that solved it!

~Marino
Flags: needinfo?(kilowit)

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.