Closed Bug 832580 Opened 12 years ago Closed 11 years ago

Windows Firefox 18.1 InternalError: too much recursion

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
18 Branch
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 794427
Tracking Flags:
Tracking Status
firefox18 - ---
firefox19 - ---
firefox20 - ---
firefox21 - ---

People

(Reporter: zwang, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17

Steps to reproduce:

Today, my windows 7 firefox was silently upgraded from 17 to 18.1.  After which we noticed that on our "heavier" ExtJS dialogs, we would get intermittent "InternalError: too much recursion" error, and the dialogs would not popup.  We confirmed that this is still working in version 17.  Did developer change how "too much recursion" is calculated?  If our customers upgrade to version 18 on windows, our web application will have problem.  The workaround is to use Chrome or IE.


Actual results:

We are getting "too much recursion" internal error in version 18.1.  We confirmed that it is working in version 17 of firefox.


Expected results:

We should not be getting the "too much recursion" internal error.
This bug does not affect Mac (Mountain Lion) Firefox 18.1.
We need a testcase with Steps to reproduce.
Another option would be that you do a regression range search but the developers would still need a testcase.
I will narrow it down.  Thanks for the link.
OS: Mac OS X → Windows 7
Assignee: nobody → general
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Worth starting by toggling the "javascript.options.ion.content" preference in about:config and seeing whether that fixes things...

It would have been really useful to get this sort of bug report before release, too.  Could I convince you to run the Aurora or Beta channel once we get this sorted out?
tracking-firefox18: --- → ?
tracking-firefox19: --- → ?
tracking-firefox20: --- → ?
tracking-firefox21: --- → ?
This bug is a duplicate of Bug 794427, which should have been fixed by Bug 803182.
We should look if we can backport the patch made for Bug 803182.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Hum, the patch made in Bug 794427 only fix the problem for debug builds, by pushing the stack limit.  So mark this bug as a duplicate of Bug 794427, which has a minimal test case likely corresponding to what ExtJS applications are doing. (knowing the previous bug with fun.caller and fun.call / fun.apply)
Hi, 
What is the current state of this bug? I have observed it in our web page. I tried it in FF v 18.0, 18.1 and now I still observe it in 18.2. It is ok in FF v 17, IE and Chrome are OK as well.
Thanks.
kanovsky, it is marked as a duplicate of this bug, https://bugzilla.mozilla.org/show_bug.cgi?id=794427  which is fixed for Firefox 21, the current Nightly release. Tomorrow, the fix should be on the Aurora release (http://www.mozilla.org/en-US/firefox/aurora/)
FYI, I just landed the fix for bug 794427 on the Firefox 20 branch. Unfortunately, it appears that I missed the cutoff for the beta 1 release coming at the end of this week. It should be in the beta 2 release, however. Sorry for the inconvenience!
Thanks for the clarification Ryan!
You need to log in before you can comment on or make changes to this bug.