When using the "at" statement, a segfault occurs when
the scheduled TimerEvent comes up. I.e. hitting the
punching bag causes segfault 5 seconds later.
While processing events, the scheduler was also able to
receive new ones, and often ended up (not clear why)
processing the same event twice. I rewrote process_events
to do its work in a copy of the event queue created at the
start of each pass through. This seems to fix the problem,
though it remains to see how it compares in terms of
performance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=15747
While processing events, the scheduler was also able to
receive new ones, and often ended up (not clear why)
processing the same event twice. I rewrote process_events
to do its work in a copy of the event queue created at the
start of each pass through. This seems to fix the problem,
though it remains to see how it compares in terms of
performance.