Hi,
Is there any way to prevent cloning an object/class of objects from being cloned while creating new thread? When i do something like:
package MyPackage;
use threads;
use threads::shared;
{
use Object::InsideOut qw(:NOT_SHARED);
};
package main;
use threads;
my $o = new MyPackage;
threads->create(\&th)->join();
sub th
{
my $o1 = new MyPackage;
}
i get:
ERROR: Attempt to DESTROY object ID 1 of class MyPackage twice
ERROR: Attempt to DESTROY object ID 1 of class MyPackage twice
Scalars leaked: 1
I assume that new thread copies $o (id = 1) into its scope and then tries to destroy it at the and along with $o1 which have the same id (1) since it's just cloned version of $o. Now, how can i prevent this? One way would be to create o _after_ thread is created (but that limits ways of using 'MyPackage' and i don't want that). Second: ensuring that $o1 would get new id (but how?). Third: ensuring that new thread would get undef as a $o value so that destroy method would not be invoked (but once again: how?).
Of course i could mark MyPackage as :SHARED but in my real app this class consist of fields which are classes that cannot be shared.
So, is there any other way to get rid of those annoying memory leaks?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|