New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CounterMutexSingleton sample crashes #3607
Comments
From ryan@bastic.netHi, please see github.com/rbastic/CounterMutexSingleton This code crashes consistently on the latest MoarVM on Mac OS X 10.9.5 It does not crash with the JVM. ab5tract has also helped to work on this and reproduce it FWIW. We can |
From @cokeOn Mon Dec 15 03:50:26 2014, ryan@bastic.net wrote:
What kind of crash? Please attach the test script here, along with the expected results, and the actual results. It would be nice if you could reduce the amount of code from 87 lines, but I understand this isn't always possible. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Fri Oct 30 06:54:00 2015, coke wrote:
Verified, segfault: $ git clone https://github.com/rbastic/CounterMutexSingleton -- |
From ryan@bastic.netHi, I'm pretty sure this is related to not mutexing / synchronizing around In talking with Jonathan before, this seemed to be a likely cause. Adding On Wed, Jul 27, 2016 at 11:15 AM, Will Coleda via RT <
|
From @timoHi, we've put in an improved error message for when libuv refuses to create an eventloop for us (for example because you've surpassed your allowance of file descriptors). Instead of segfaulting when accessing the NULL it returned instead of the eventloop, we'll throw an exception for you. With the very latest moarvm, behaviour is now this: timo@schmand /tmp> perl6 CounterMutexSingleton.pl6 --num_threads=252 Setting the default num_threads to 100000 is ... quite optimistic to say the least :) |
From @timoNow the exception also contains the error as reported by libuv: timo@schmand /tmp> perl6 CounterMutexSingleton.pl6 --num_threads=253 I think this bug can now be closed; any other problems with this code should be reported in a different ticket, IMO, because i'd like to make this the ticket for "segfault when too many threads are created". Cheers! |
From ryan@bastic.netSounds good! Thanks. On Thu, Feb 23, 2017 at 12:21 PM, Timo Paulssen via RT <
|
From ryan@bastic.netIndeed :) It was just a simple test case to demonstrate some things to Thanks for your work! On Thu, Feb 23, 2017 at 11:53 AM, Timo Paulssen via RT <
|
From @dogbert17On Thu, 23 Feb 2017 09:01:40 -0800, ryan@bastic.net wrote:
Closing issue, better late than never. |
@dogbert17 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#123434 (status was 'resolved')
Searchable as RT123434$
The text was updated successfully, but these errors were encountered: