[TIMOB-397] setInterval bug
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:52:55.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.3.0 |
| Components | iOS |
| Labels | n/a |
| Reporter | Nolan Wright |
| Assignee | Jeff Haynie |
| Created | 2011-04-15T02:28:40.000+0000 |
| Updated | 2011-04-17T01:52:55.000+0000 |
Description
If you run setInterval repeatedly with a low interval (100 milliseconds or less), it eventually stops firing
Comments
- Nolan Wright 2011-04-15
check set interval test under platform. i fire every 10 milliseconds and update the count on the UI. it is sometimes are to reproduce (i.e., sometimes the count gets as high as 14,000 before stopping)
- Jeff Haynie 2011-04-15
note that granularity of less than 30ms it seems is not guaranteed on iphone scheduler.
- Nolan Wright 2011-04-15
Blain - we need this one fixed
- Jeff Haynie 2011-04-15
(from [6e6faeece13e88d360a5b9fd50d39fafe8d6d89d]) Closes #397 and hopefully stops other race conditions http://github.com/appcelerator/titanium_mobile/commit/6e6faeece13e88d360a5b9fd50d39fafe8d6d89d"> http://github.com/appcelerator/titanium_mobile/commit/6e6faeece13e8...