Joe has already verified it. Case #42044 (not 42046!).
case 34956
What a pity. It seems the problem has not been fixed in 2016r1. Still 1Mega increase each time a void window is opened.
@Ulrich Bogun [quote] and you might have seen it’s marked fixed in Feedback now, which makes me think the condition in the code above wont have to be modified and the fix will be in 2016r1.[/quote]
@Joe Ranieri [quote]Assuming the fix didn’t cause any unexpected regressions, it should be in 2016r1.[/quote]
[quote=238731:@Eli Ott]Just add this to the close event of window2:
Declare Sub release Lib "Foundation" Selector "release" (receiver As Ptr)
release(Ptr(Handle))[/quote]
That really helped, thank you very much!
Had a look today at my app and found out that after opening and closing a window about 20 times (that a “real” user will open and close maybe a hundred times a day, maybe more) I “lost” about 120MB of RAM to … nothing. Put that fix in there - gone. PLEASE, Xojo, do something about it. I can imagine that “hack” might induce problems when it’s finally fixed but … it’s been around some time, right?
In FeedBack, case #43484, is ranked 606, and case #42044 is ranked 826.
If you have not yet done it, please add your vote. Thanks.