Debugging a (JavaScript) "Maximum call stack size exceeded" exception
Hi everybody, I have a question loosely related to WebKit, but I hope someone could share some useful knowledge. I am working on a JavaScript framework. Testing the framework with FireFox everything works as expected. Using Safari I get a "Maximum call stack size exceded". I have investigated this issue and find out that FireFox JavaScript interpreter has a much deeper (1000) stack size than Safari (100). Using FireBug (a FireFox extension to degub JavaScript) I have tried to get the full stack-trace of the execution in the point where presumably Safari was hitting the stack limit. To my surprise, the stack trace I got was only 65 level deep. I have tried to run the latest nightly build with Drosera attached, but no useful information is provided in my case. Is there a way in Safari to get a full stack-trace of the execution of a JavaScript in the event of an exception like the one I am facing? Thanks for your attention. Best regards, Giulio Cesare Solaroli
Drosera will be able to provide this information soon enough. Bug 4045: JavaScript call stack limit of 99 is too small for some applications; needs to be closer to 500 http://bugzilla.opendarwin.org/show_bug.cgi?id=4045 — Timothy Hatcher On Jul 8, 2006, at 5:09 AM, Giulio Cesare Solaroli wrote:
I have tried to run the latest nightly build with Drosera attached, but no useful information is provided in my case.
Is there a way in Safari to get a full stack-trace of the execution of a JavaScript in the event of an exception like the one I am facing?
Timothy, thank you very much for the valuable information. Giulio Cesare On 7/8/06, Timothy Hatcher <timothy@hatcher.name> wrote:
Drosera will be able to provide this information soon enough.
Bug 4045: JavaScript call stack limit of 99 is too small for some applications; needs to be closer to 500 http://bugzilla.opendarwin.org/show_bug.cgi?id=4045
— Timothy Hatcher
On Jul 8, 2006, at 5:09 AM, Giulio Cesare Solaroli wrote:
I have tried to run the latest nightly build with Drosera attached,
but no useful information is provided in my case.
Is there a way in Safari to get a full stack-trace of the execution of
a JavaScript in the event of an exception like the one I am facing?
participants (2)
-
Giulio Cesare Solaroli
-
Timothy Hatcher