-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
MemoryLeak: Charge sorter #3165
Comments
There should be one instance to hold the changes. Now not multiple ones. |
Not sure if this is related, but the window title suggests a similar issue: "a SpecWindow(784367360) named: Dual Change Sorter on: Unnamed on: Unnamed on: Unnamed" (I'd expect only one "on: Unnamed") |
Yes :) |
It will be fixed with spec 2 synch |
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. If no further activity occurs, it might be closed. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
|
Still valid |
I don't think this is a memory leak, Of course, please reopen if there is a concrete issue we can deal with. |
In an image, I worked on Change Sorter and after I finished I ran some GC but I still had instances in my image.
It's possible we have a memory leak.
The text was updated successfully, but these errors were encountered: