-
1 Mar 2012 5:07 AM #1Ext JS Premium Member
- Join Date
- Apr 2008
- Location
- Groningen - Netherlands
- Posts
- 1,017
- Vote Rating
- 23
[4.1B3] TaskManager doesn't break on runtime errors, but causes infinite loop
[4.1B3] TaskManager doesn't break on runtime errors, but causes infinite loop
REQUIRED INFORMATION
Ext version tested:- Ext 4.1 Beta3
Browser versions tested against:- FF3 (firebug 1.3.0.10 installed)
DOCTYPE tested against:- ____
Description:- If I run a js function that produces a runtime error with the taskmanager, the interval is ignored and an infinite loop is the result. This is very annoying while debugging, especialy if the runtime error is caused by an Ajax request
Steps to reproduce the problem:- Run the sample and see the log in firebug
The result that was expected:- The application or TaskManager should break
The result that occurs instead:- It loops
Test Case:
Code:function withError() { console.log('function with error'); var error = undefinedVar; } Ext.TaskManager.start({ scope: this, run: withError, interval: 4000 });
-
1 Mar 2012 12:55 PM #2
Thanks for the report. I've opened a ticket for this.
The expected behavior should match that of setInterval given the same callback function should it not?
The goal of TaskRunner is just to reduce the number of timers managed by the browser since they can be expensive (esp on old IE).Don Griffin
Ext JS Development Team Lead
Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue
"Use the source, Luke!"
-
5 Mar 2012 2:26 AM #3Ext JS Premium Member
- Join Date
- Apr 2008
- Location
- Groningen - Netherlands
- Posts
- 1,017
- Vote Rating
- 23
Yes, with window.setInterval the interval is not ignored. That is much better while debugging.
Code:function withError() { console.log('function with error'); var error = undefinedVar; } window.setInterval(withError, 4000);
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-5496
in
4.1.


Reply With Quote