[perl #125656] [CONC] Creating too many Proc::Async objects fills the file descriptor table, which causes libuv to abort()

This only applies if you call .stdout or .stderr *and* never close them.

[perl #125757] shell().exitcode is always 0 when :out is used

This has been resolved since 2017.06

[perl #128594] [SEGV] attempting to use :merge when run()ning an external command causes a core dump

Resolved in https://github.com/rakudo/rakudo/commit/c86090e `perl6 -e 'run("ls", :merge).out.slurp.say'`

[perl #131510] [SEGV] Segfault when `-Ilib` while running a file that does `use lib ` and loads some modules

This appears to be resolved - possibly in https://github.com/rakudo/rakudo/commit/37250ed5ebc3d25eae656ddfa19187c90a712e3c

[perl #131745] Wrong rakudo's INSTALL.txt instructions mention non-existent --with-moar option

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131745] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131745 > https://irclog.perlgeek.de/perl6/2017-07-12#i_14861594

[perl #131740] [BUG] Concurrent threads report same Thread ID post-await

On Tue, 11 Jul 2017 15:30:40 -0700, emmil...@gmail.com wrote: > I'm using the new scheduler behavior described here: > > https://github.com/rakudo/rakudo/pull/1004 > > After an "await" on a managed (non-main) thread it appears that > execution > may continue on a different thread than it began on

[perl #131740] [BUG] Concurrent threads report same Thread ID post-await

On Tue, 11 Jul 2017 15:30:40 -0700, emmil...@gmail.com wrote: > I'm using the new scheduler behavior described here: > > https://github.com/rakudo/rakudo/pull/1004 > > After an "await" on a managed (non-main) thread it appears that > execution > may continue on a different thread than it began on