I'm sharing nested hashes. Now when a new element becomes available, the old threads don't see it: 
#!/usr/bin/perl

use warnings;
use strict;
use threads;
use threads::shared;
use Data::Dumper;

my $href = &share({});
$href = {};

sub sub1 {
  sleep 1;
  print threads->tid();
  print Dumper $href;
}

$href->{a} = &share({});
$href->{a} = {};

my $th1 = threads->new('sub1');
$href->{b} = &share({});
my $th2 = threads->new('sub1');

$th1->join();
$th2->join();

[download]
New th2 sees all values, whereas old th1 only sees the first one: 
1$VAR1 = {
          'a' => {}
        };
2$VAR1 = {
          'a' => {},
          'b' => {}
        };

[download]

In reply to Re^10: does threads (still) memleak? by faxm0dem
in thread does threads (still) memleak? by faxm0dem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.