On Thu, 21 Sep 2006, Michael Burns wrote: > As far as I can tell, even with current Masons, this is still an > issue for the test case I outlined in this thread: > > http://sourceforge.net/mailarchive/message.php?msg_id=11948234 > > I found it particularly occurs within sight of component-with-content > calls.
Actually, that's a _different_ bug. I've just tracked it down to Mason's caching of compiled components. If you clear the code cache the object in question gets cleaned up. That's a big WTF. Back on the original thread I blamed it on Perl but now I think it's Mason's fault. Unfortunately, fixing it could be very challenging. -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
