From: Panayotis K. <pan...@pa...> - 2010-05-24 17:09:32
|
On 24 Μαϊ 2010, at 7:16 μ.μ., Joshua Melcon wrote: > Hi Panayotis, > > I am aware of this issue and have been working on a fix for it. > Sadly, the fix is non trivial though I am making (slow) progress on > it. > > For now, the best workaround is to comment out > // new ExcessRetainsOptimization().Process(curRun.allCodePaths, curRun.beenTo, > // codeElement); > > in ReferenceCounting.java. > > Since this bug is affecting people, I will talk to Arno about checking > in that workaround until I can actually implement a correct fix. > > Sorry you encountered this… The good thing is someone is working on it (the bad is that I spent 4 hours to understand why my application didn't work with latest version of xmlvm :-o ) As with my previous e-mail, I'll suggest a simple fix for this: every time an object is referenced this way, retain this object and keep track of it, as with other objects. When this is no longer needed, release it. Probably of course it gets more complex than this :) For now, I preferred to do it the "hard" way - just retain this object and release it later on (yes, yes, with my newest shiny patch :P ) |