User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux; en_US) KHTML/3.5.5 (like Gecko) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.8) Gecko/20061116 Firefox/1.5.0.8 Using the some capabilities of the Web Developer extension on forms with large hidden inputs (5K+) causes firefox to crash, and kills the X server as well. Apparently Web Developer is just doing straight forward DOM manipulation. Reproducible: Always Steps to Reproduce: 1. Make sure you've saved and shut down anything important. 2. Load up http://jobsearch.nz.hudson.com/jobsearch/search.aspx 3. Using webdeveloper do either: 3a. Forms -> Display Form Details or 3b. Forms -> View Form Information 3c. Click on the tab for the orginal page after being shown the form info. Actual Results: Firefox crashes. The X server restarts. Expected Results: 3a. the details of the form should be added to the rendered page. 3c. the tab showing the original rendered page should show. 64bit 2.6.17 linux kernel running on an amd64 xorg-x11 version 7.1 Web Developer version 1.0.2 Saving the problematic page and changing the '__VIEWSTATE' input to something short gives you a page that doesn't crash firefox.

Does Web Developer try to show the value of the hidden field? X has bugs when you try to display a bunch of text at once (without wrapping). I think Firefox works around those bugs successfully (or at least avoids crashing) on trunk and maybe also in Firefox 2. See bug 302294 and dependencies.

(In reply to comment #1) > Does Web Developer try to show the value of the hidden field? Yes. In reproduction case 3a it (attempts to) show the hidden field in the original rendered page. This crashes firefox, and X, as soon as it tries. In reproduction case 3b, 3c it successfully shows the hidden field in a newly opened tab, though the text is layered up on top of itself in a limited space. It's when you leave that new tab by clicking on the original rendered page's tab that it crashes in this scenario.

Is it better in Firefox 2 or on trunk?

(In reply to comment #3) > Is it better in Firefox 2 or on trunk? I haven't had a chance to test it. The root cause of the problem seems to be a bug in the nvidia drivers I was using. The page at http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=1971 explains the nvidia bug and an X server bug with similar symptoms. Having upgraded my nvidia drivers from 1.0.8774 to 1.0.8776 firefox 1.5 doesn't crash. Though there is rendering weirdness, eg the string appearing and disappearing when you scroll, change tabs etc etc. As to whether trunk or version 2 has a successful work-around... if it would give you useful info I can try and downgrade nvidia and install v2 to test it when I get some free time.

Are we able to close this bug now?

do you still see this problem using FF 3.5 beta**, or FF 3.0 started in safe mode***? If yes, please comment If not, please close with resolution set to WORKSFORME or INVALID (if problem was extension or the like) ** http://www.mozilla.com/en-US/firefox/all-beta.html *** http://support.mozilla.com/en-US/kb/Safe+Mode

No reply, INCO. Reporter, please reopen this bug if you can see this issue with Firefox 3.5 or later in Firefox Safe Mode (http://support.mozilla.com/kb/Safe+Mode) or a new profile (http://support.mozilla.com/kb/Profiles)