Skip to content
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

Open
jecisc opened this Issue Apr 11, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@jecisc
Copy link
Member

commented Apr 11, 2019

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.

@Ducasse

This comment has been minimized.

Copy link
Member

commented Apr 21, 2019

There should be one instance to hold the changes. Now not multiple ones.

@akgrant43

This comment has been minimized.

Copy link
Collaborator

commented Apr 22, 2019

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")

@Ducasse

This comment has been minimized.

Copy link
Member

commented Apr 22, 2019

Yes :)

@jecisc

This comment has been minimized.

Copy link
Member Author

commented Apr 22, 2019

It will be fixed with spec 2 synch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.