Re: Timer scheduling and cancel-timer

[Stephen Berman]

On Mon, 21 Jan 2013 19:50:44 -0800 "Drew Adams" <address@hidden> wrote:

>> It happened over and over and over: as soon as I quit the debugger
>> it popped up again.
>>
>> > Until recently timer-event-handler just silently dropped all errors
>> > signaled by timers, whereas I recently changed it to turn them into
>> > messages (a nd to show the backtrace if debug-on-error is non-nil).
>> > 
>> > So maybe this error has been present for ever but just got unnoticed
>> > until now.  The "#[nil ...]" seems to be the unadvised body of
>> > show-paren-function, so the error apparently comes from within
>> > show-paren-function.
>
> FWIW, I have been treated to this infinitely repeating backtrace several times
> now.
>
> Perhaps it is worth reverting the code change you made that makes this happen
> now, until you find the bug?
>
> I'm kind of surprised that no one else seems to be running into this problem.
> Each time it arises, point follows a right paren, I believe.

I hit it several times after updating from the trunk on 17 January but
didn't have time to try to debug it, and also couldn't find a reliable
recipe for reproducing it.  Anyway, for whatever reason, I haven't seen
it again for a couple of days (with the same build).

Steve Berman