fbrm@monastery:~$ perl -MData::Dumper -E '$Q=$A[4][6]; say Dumper \@A' $VAR1 = [ undef, undef, undef, undef, [] ];
See how there are many undef's in the array (not sparse)... so you must change your code to probe first for existence of the array spot, and only then ask for the value (to avoid autovivification). Now, when creating the AoA, you also get this (perl -MData::Dumper -E '$A[4][6]=11;say Dumper \@A') so maybe switch to Hashes/HoH?
EDIT: added a better example with seemly only a 'read', here is the old example, which is clearly an assign:
fbrm@monastery:~$ perl -MData::Dumper -E '$A[4]="hi"; say Dumper \@A' $VAR1 = [ undef, undef, undef, undef, 'hi' ];
edit2: You can check this hypothesis with profiling heap memory usage on perl
In reply to Re: Win10: Getting popup "Perl Interpreter has stopped working"
by FreeBeerReekingMonk
in thread Win10: Getting popup "Perl Interpreter has stopped working"
by AllBackJack
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |