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.

Sign up for GitHub

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

Jump to bottom

Potential memory leak #211

Open
NickGeek opened this issue Mar 17, 2020 · 1 comment
Open

Potential memory leak #211

NickGeek opened this issue Mar 17, 2020 · 1 comment
Labels
bug
Projects
Creepy Crawlies

Comments

@NickGeek
Copy link
Member

It seems like TextArea's may still have an active event listener on them.
@NickGeek NickGeek changed the title Potentail memory leak Potential memory leak Mar 18, 2020
@NickGeek NickGeek added the bug label Apr 3, 2020
@NickGeek NickGeek added this to Needs triage in Creepy Crawlies via automation Apr 3, 2020
@NickGeek NickGeek moved this from Needs triage to High priority in Creepy Crawlies Apr 3, 2020
@NickGeek NickGeek moved this from High priority to Medium Priority in Creepy Crawlies Apr 3, 2020
@zdens
Copy link

zdens commented Jun 22, 2020

I'm observing an increasing memory consumption while micropad window is opened and active and the TextArea is active.
After micropad window is closed an extra memory is freeing.
the observation was performed by means of KDE System Monitor.

@NickGeek NickGeek added this to the MicroPad v4 milestone Jun 28, 2021
NickGeek added a commit that referenced this issue Jan 8, 2022
@NickGeek
Simplifying the markdown element to hopefully reduce the risk of #211
51f27a8
@NickGeek NickGeek removed this from the MicroPad v4 milestone Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
Creepy Crawlies
Status: Medium Priority
Creepy Crawlies
  
Medium Priority
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NickGeek @zdens