Closed Bug 242919 Opened 21 years ago Closed 21 years ago

full browser freeze then segfaults when hitting tab, probably because of JS code

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: s.loeuillet, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Epiphany/1.2.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Epiphany/1.2.5 freeze + segfault when filling a web form, probably JS related (to be precise : when hitting tab to go to next field, which is monitored by a JS function) Reproducible: Always Steps to Reproduce: filling the form, hitting tab to navigate between fields the field just after "Numéro de téléphone GSM" is the faulty one when hitting tab from the "GSM" field, the browser freeze about 1 minute later, it segfaults Actual Results: complete browser freeze, later, i have a segfault Expected Results: beeing able to fill in the form without crashing mozilla :) on this field, there is a JS code that show how many chars you're allowed to type. (default = 1500 chars) reproduced this bug with both mozilla and mozilla+epiphany look at JS function "Compter" in the source, might be the faulty one
can you reproduce this with 1.7RC1 ?
I can't find any field that mentions "GSM" at the URL. Stephane, does the problem still occur in Firefox 1.0 or Mozilla 1.7.x?
either the JS script changed or the problem was fixed long ago in mozilla i now use firefox 1.0 (final), and it works fine, closing
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
OK, thanks for testing, it works for me too. We use WORKSFORME when we don't know exactly which code change that fixed it...
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
-> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.