Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJS-5496
in
a recent build.
-
[4.1B3] TaskManager doesn't break on runtime errors, but causes infinite loop
REQUIRED INFORMATION
Ext version tested:
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:
Test Case:
Code:
function withError() {
console.log('function with error');
var error = undefinedVar;
}
Ext.TaskManager.start({
scope: this,
run: withError,
interval: 4000
});
-
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
"Use the source, Luke!"
-
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);