-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memory leak in Tandem.removePhetioObject #203
Comments
This is blocking ph-scale RC, see phetsims/ph-scale#199. |
This is blocking ph-scale RC, see phetsims/ph-scale#199. Milestone for 1.4 publication is ?? This is blocking natural-selection prototype RC, see phetsims/natural-selection#205. Milestone for publication is "this week if possible". |
The patch disposes of the Tandem in every brand, not just in phet-io. It looks correct to me, leaving assigned to @zepumph to confirm. |
I decided to commit the proposal, still ready for review. |
This change looks good to me. I would also add that this is better to dispose after calling phetioObjectRemoved listeners because those listeners may depend on the tandem (like phetioAPIValidation.onPhetioObjectRemoved). Good catch and thanks for the implementation. I did not test to confirm that it fixed the memory leak. I only looked at the code. |
Any rc taken after 5/1 would be effected by this. I know that means at least:
@Denz1994 I'm unsure about BaM This fix should be very simple though, just cherrypick dc10b03. This issue effects |
Assigning to @Denz1994 and @chrisklus to determine if their RC was made after 5/1. If so to apply the patch, either in this issue or a sim-specific one. The patch is dc10b03. |
Any RC with shas after 5/1 has a memory leak in phet brand in #203. I know of only what I spoke of above. Assigning to @ariel-phet to make sure that this doesn't effect other sims published. Likely there are prototypes that effect this, but maybe we don't care about memory leaks in those. |
Shouldn't we use the batch maintenance release process to automatically identify all live branches with this bug and automatically or semi-automatically fix them? (This question goes for all bugs fixed during any RC). |
Is this issue ready for verification in Natural Selection, so that I can resolve phetsims/natural-selection#205 and move forward with prototype publication? |
Yes, please pull and test to confirm this is ready for Natural Selection. This has been fixed and reviewed in master. The only reason this issue remains open is to see what branches it may need to be cherry-picked to. |
Memory tests look good for both NS brands, see phetsims/natural-selection#189 and phetsims/natural-selection#190. Closing. |
Oops. Reopening because @samreid said:
|
Agreed. EFAC will be taken (was taken yesterday?) from master. I think all that is left is to do is for @Denz1994 to patch BAM if needed. |
Thanks, @zepumph for the direction. This was patched in BAM. Removing my assignment. |
Sounds good. I don't any other sims are in RC right now. Over to @ariel-phet to confirm and close |
I think we are good here, closing |
Over in phetsims/natural-selection#189 (comment), I identified a huge memory leak in Natural Selection due to PhET-iO, even with
brand=phet
. I determined that 0 instances of Tandem and DynamicTandem were being deleted.@samreid helped me identify the source of the problem. The leak was introduced on 5/1/2020 in 571cc87 for #176. It affects all sims that have been published since then.
@samreid provided the patch below, which I confirmed address the leaking of Tandem and DynamicTandem in natural-selection. This patch needs to be reviewed by @zepumph, with top priority.
patch
Then we need to identify which sims have been published with this problem, decide which to patch, schedule maintenance releases, etc.
Assigning to @jbphet because this leak is almost certainly present in the recently-published SOM.
The text was updated successfully, but these errors were encountered: