<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1. We have the same issues here, and also moved to erlang:send_after.<div>We still use timer:send_interval but just for small intervals.<div><br><div><div>On 19/06/2011, at 23:02, Ryan Huffman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I ran into a lot of problems with the timer module on R14B02 and eventually switched to using erlang:send_after. This particular section in the erlang doc also convinced me to switch over to erlang:send_after and maintain my own timer: <a href="http://www.erlang.org/doc/efficiency_guide/commoncaveats.html#id58959">http://www.erlang.org/doc/efficiency_guide/commoncaveats.html#id58959</a><div>
<br></div><div>I was running on a 64-bit system (CentOS 5.5), so, as Dale mentioned, the problem may be fixed.</div><div><br></div><div>Ryan</div><div><br><div class="gmail_quote">On Sun, Jun 19, 2011 at 5:00 PM, Dale Harvey <span dir="ltr"><<a href="mailto:dale@arandomurl.com">dale@arandomurl.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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<br>
<br><a href="http://erlang.org/pipermail/erlang-bugs/2011-April/002294.html" target="_blank">http://erlang.org/pipermail/erlang-bugs/2011-April/002294.html</a><br>
<br>That may be your problem?<div><div></div><div class="h5"><br><br><div class="gmail_quote">On 19 June 2011 03:43, Zsolt Keszthelyi <span dir="ltr"><<a href="mailto:zsolt.erl@gmail.com" target="_blank">zsolt.erl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear All,<br>
<br>
I ran into something in R14B02.<br>
It looks like if I start a timer with a long interval then all previously started timers stop.<br>
The timer server is still running and the timers are in the ETS table.<br>
No error returned. Nothing crashes.<br>
This was working on R13B03 and is not working on R14B02<br>
The long interval is exactly 2^31/1000 ms.<br>
Is it a bug or an intentional change?<br>
Maybe the timer module was never meant to be used with long intervals but shouldn't it give at least an error msg.?<br>
<br>
Code:<br>
<br>
%% works on R13B03<br>
%% doesn't work on R14B02<br>
<br>
-module(timerbug).<br>
<br>
-compile(export_all).<br>
<br>
start()-><br>
timer:apply_interval(1000, io, format, ["Hello!\n"]),<br>
timer:sleep(5000),<br>
timer:apply_interval(40*60*<u></u>1000, io, format, ["No more hello.\n"]).<br>
<br>
______________________________<u></u>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a><br>
</blockquote></div><br>
</div></div><br>_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></div></div></body></html>