PDA

View Full Version : Insane number of timers: 501 crash



Michael Dubno
2004-07-06, 19:36
It seems that 5.2.1 introduced a new bug - "Insane number of timers: 501"
which did not occur in earlier version. My guess is that this is being
triggered by my use of the slim devices to send frequent display updates of
weather. Each update has a timeout set to prevent the display of stale data
over time. Perhaps the perl code for resetting or halting the timer got
modified in the last few weeks.



Does any of this make sense?



Thanks - Mike

Dan Sully
2004-07-06, 19:38
* Michael Dubno <michael (AT) dubno (DOT) com> shaped the electrons to say...

>It seems that 5.2.1 introduced a new bug - "Insane number of timers: 501"
>which did not occur in earlier version. My guess is that this is being
>triggered by my use of the slim devices to send frequent display updates of
>weather. Each update has a timeout set to prevent the display of stale data
>over time. Perhaps the perl code for resetting or halting the timer got
>modified in the last few weeks.

Michael - perl can only have one active alarm() statement at any one time.
Each new call to alarm() will reset the timer. Might that be causing your problem?

-D
--
<gldnmean> Being around marketing could be interesting, if they're released
into a death trap filled labyrinth while you hunt them for sport

Dan Sully
2004-07-06, 19:41
* Dan Sully <daniel (AT) electricrain (DOT) com> shaped the electrons to say...

>* Michael Dubno <michael (AT) dubno (DOT) com> shaped the electrons to say...
>
>>It seems that 5.2.1 introduced a new bug - "Insane number of timers: 501"
>>which did not occur in earlier version. My guess is that this is being
>>triggered by my use of the slim devices to send frequent display updates of
>>weather. Each update has a timeout set to prevent the display of stale
>>data
>>over time. Perhaps the perl code for resetting or halting the timer got
>>modified in the last few weeks.
>
>Michael - perl can only have one active alarm() statement at any one time.
>Each new call to alarm() will reset the timer. Might that be causing your problem?

Or rather (after looking at the code) - are you killing your timers after creating them?

See Slim/Utils/Timers.pm

-D
--
It does not do to leave a live Dragon out of your calculations..