Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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?

In reply to Prevent object from cloning by menth0l

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (2)
As of 2024-04-26 00:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found