From @zoffixznet

<moritz> m​: 7 ~ "\x[308]" x 100_000
<camelia> rakudo-moar 7925d6​: OUTPUT«WARNINGS for <tmp>​:␤Useless use of "~" in expression "7 ~ \"\\x[308]\" x" in sink context (line 1)␤»
<moritz> m​: 7 ~ "\x[308]" x 150_000
<camelia> rakudo-moar 7925d6​: OUTPUT«(signal SEGV)»

From @zoffixznet

To add to the ticket my mild digging into this​: https://irclog.perlgeek.de/moarvm/2016-09-13#i_13205266

From @jnthn

On Thu, 08 Sep 2016 03​:44​:55 -0700, cpan@​zoffix.com wrote​:

<moritz> m​: 7 ~ "\x[308]" x 100_000
<camelia> rakudo-moar 7925d6​: OUTPUT«WARNINGS for <tmp>​:␤Useless use
of "~" in expression "7 ~ \"\\x[308]\" x" in sink context (line 1)␤»
<moritz> m​: 7 ~ "\x[308]" x 150_000
<camelia> rakudo-moar 7925d6​: OUTPUT«(signal SEGV)»

I've put a limit on the number of combiners allowed (1024, waaay higher than any real-world use case will need). So it now throws rather than SEGVs. Added a test to S15-nfg/many-combiners.t to check that it either works or throws a catchable exception. We may in the future want to specify a minimum number that a Perl 6 implementation must be able to cope with. For now, the SEGV is gone.

/jnthn

The RT System itself - Status changed from 'new' to 'open'

@jnthn - Status changed from 'open' to 'resolved'