"Can you cut the code down to something that shows that its actually 'detach' thats breaking it"
Okay, that's easy. It only took me 1 minute to come up with this code, and break (core dump) it: (I repeated 3 times to make sure it is really broken)
use strict; use warnings; use threads; for (my $i = 1; $i < 1000; $i ++) { threads->create(\&abc)->detach(); } sub abc { }
Update:
It was a waste to create 1000 threads, and side tracks people's focus. This is much more simple and clear:
use strict; use warnings; use threads; for (my $i = 1; $i < 3; $i ++) { threads->create(\&abc)->detach(); } <>; sub abc { }
Update 2:
The testing is done on win32, using .2. This was mentioned in the first stream of notes Perl 5.8.2 thread is much worse on .2 threads. Any way, I should have repeated this here earlier.
In reply to Re: Re: Perl 5.8.2 thread is worse - more findings from today
by pg
in thread Perl 5.8.2 thread is worse - more findings from today
by pg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |