[erlang-questions] Weird problem with "receive after ..."
Sat Oct 19 21:51:25 CEST 2013
I don't know if a work around probably make sure you are running the most recent version of virtual box? And make make sure to give it multiple cores. You could also convert the vm to a different format (like VMware), and see if it works better.
On Oct 18, 2013, at 1:29 PM, Ferenc Holzhauser <ferenc.holzhauser@REDACTED> wrote:
> Hi Anthony,
> That must be it: it is running in virtualbox indeed. Are you aware of any workaround/fix to try? I'm quite attached to this VM setup. Would be great if I could make it work reliably.
> On Oct 18, 2013 9:35 PM, "Anthony Molinaro" <anthonym@REDACTED> wrote:
>> Are you running in some sort of virtualized environment. I seem to recall noticing some oddness with timer:send_interval/2 under VMware at one point, but it's a total guess so may not be your issue at all.
>> On Oct 18, 2013, at 11:50 AM, Ferenc Holzhauser <ferenc.holzhauser@REDACTED> wrote:
>> > Hi,
>> > On my development system sometimes "receive after..." starts hanging after a while.
>> > I know "sometimes" is not very helpful but I couldn't find any obviously related event yet that might trigger it.
>> > From that point it stops working in the whole VM e.g. I can type "receive after 10 -> ok end." in the shell and watch it never returning. Of course it also breaks most of the things that need timer.
>> > Normal receive keeps working fine, the issue is related to timeout only.
>> > It is R16B01 and I'm not using any self made NIFs, drivers or other funny things that could break the VM.
>> > Thank you for any hints or suggestions about the possible reason/fix in advance.
>> > Regards,
>> > Ferenc
>> > _______________________________________________
>> > erlang-questions mailing list
>> > erlang-questions@REDACTED
>> > http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions