mirror of
https://github.com/denoland/deno.git
synced 2024-12-21 23:04:45 -05:00
93b7acf99d
When the global timer fires earlier than expected, which apparently happens sometimes on server editions of Windows, we didn't call any setTimeout callbacks, but we *also* didn't reschedule the global timer to fire again later. When this situation occurred it would make deno exit abruptly if there were no other asynchronous ops running on the event loop. It could also lead to application hangs if the upcoming setTimeout callback was critical for the application to make progress. |
||
|---|---|---|
| .. | ||
| compiler.rs | ||
| dispatch_json.rs | ||
| dispatch_minimal.rs | ||
| errors.rs | ||
| fetch.rs | ||
| files.rs | ||
| fs.rs | ||
| io.rs | ||
| metrics.rs | ||
| mod.rs | ||
| net.rs | ||
| os.rs | ||
| performance.rs | ||
| permissions.rs | ||
| process.rs | ||
| random.rs | ||
| repl.rs | ||
| resources.rs | ||
| timers.rs | ||
| workers.rs | ||