DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
Thanks for the report. Indeed, this is true (Linux/Unix only) and has been
fixed in FLTK 1.4 (Git master, commit 35a3e7cc16f8) but not backported. See
also STR #3516 (which is about more than only this aspect).
The fix in FLTK 1.4 was to just clear 'missed_timeout_by' w/o saving and
restoring the value (as you propose) because it seems to be unnecessary. It
was a fault not to clear the missed_timeout_by value at all (except
overwriting it when serving the next timeout).
Do you have evidence that the value should be saved and restored, or was
this only kinda "defensive programming"?
I'm not sure if we should backport this to 1.3: after all it's not a
serious bug, it's only prio 3 (moderate).
[ Direct Link to Message ]