[erlang-questions] bug in timer module in R14B02?

[Dale Harvey]

I believe there was an integer overflow bug on 64 bit systems that affect
ordered ets tables (and therefore caused timers not to trigger) in R14B02

http://erlang.org/pipermail/erlang-bugs/2011-April/002294.html

That may be your problem?

On 19 June 2011 03:43, Zsolt Keszthelyi <zsolt.erl@REDACTED> wrote:

> Dear All,
>
> I ran into something in R14B02.
> It looks like if I start a timer with a long interval then all previously
> started timers stop.
> The timer server is still running and the timers are in the ETS table.
> No error returned. Nothing crashes.
> This was working on R13B03 and is not working on R14B02
> The long interval is exactly 2^31/1000 ms.
> Is it a bug or an intentional change?
> Maybe the timer module was never meant to be used with long intervals but
> shouldn't it give at least an error msg.?
>
> Code:
>
> %% works on R13B03
> %% doesn't work on R14B02
>
> -module(timerbug).
>
> -compile(export_all).
>
> start()->
>    timer:apply_interval(1000, io, format, ["Hello!\n"]),
>    timer:sleep(5000),
>    timer:apply_interval(40*60***1000, io, format, ["No more hello.\n"]).
>
> ______________________________**_________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110620/5824e701/attachment.htm>