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

Memory leak? #17

Open
mjmeintjes opened this issue Nov 19, 2020 · 2 comments
Open

Memory leak? #17

mjmeintjes opened this issue Nov 19, 2020 · 2 comments

Comments

@mjmeintjes
Copy link

I've been using reveal pretty extensively and it works very well.

However, I have been experiencing lots of OutOfMemory exceptions, and I wonder whether reveal is the cause.

Is there some sort of limit on the number of history items to store? If not, it would be useful to be able to set a limit on the amount of entries to keep in memory (like a ring buffer). Is this something that would be possible?

@vlaaad
Copy link
Owner

vlaaad commented Nov 20, 2020

Reveal can be the cause, yes — it saves references to all submitted values for inspection. I'm planning to add the ability to clear the output panel, so those refs can be garbage collected

@vlaaad
Copy link
Owner

vlaaad commented Dec 9, 2020

Released 1.1.171 that adds Ctrl L as a shortcut for clearing the output panel. It uses Ctrl (instead of ) on Mac too for consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants