20,741
edits
Nasal Events: Difference between revisions
Jump to navigation
Jump to search
m
→Summary
m (→Summary) |
m (→Summary) |
||
| Line 5: | Line 5: | ||
* Often, people end up instantiating multiple loops/callbacks accidently, without really noticing it on fast systems | * Often, people end up instantiating multiple loops/callbacks accidently, without really noticing it on fast systems | ||
* In addition, the simulator may instantiate multiple callback instances through signals (i.e. during reset/relocating) | * In addition, the simulator may instantiate multiple callback instances through signals (i.e. during reset/relocating) | ||
* Multiple rogue Nasal | * Multiple rogue Nasal callback instances invoked through timers or listeners may considerably slow down the simulator and require a complete restart on some systems | ||
* This issue is currently very hard to detect, because we only have a single "events" subsystem that shows up in the system monitor | * This issue is currently very hard to detect, because we only have a single "events" subsystem that shows up in the system monitor | ||
* The system monitor does not provide any info about the number of callbacks, or their nature/origin | * The system monitor does not provide any info about the number of callbacks, or their nature/origin | ||