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 present on 1.8 #1010

Closed
felixsanz opened this issue Jun 3, 2017 · 1 comment
Closed

Memory leak present on 1.8 #1010

felixsanz opened this issue Jun 3, 2017 · 1 comment
Labels
bug Unexpected problem or unintended behavior
Milestone

Comments

@felixsanz
Copy link

felixsanz commented Jun 3, 2017

I have my system configured so it spawns weechat on a terminal at login.

I also have encrypted sec.info data, so when weechat starts, it asks me for the password.

Well, it happened me twice that, instead of giving the password, i just closed the terminal window directly (because i didn't want to use weechat that time), and after few seconds (30-90s) i start hearing the fan of my laptop like a turbine. I take a look at the temperatures and the CPU is at 90ºC!! Because the CPU is working at 100% load. I take a look at top and the process eating that much CPU is weechat. So i kill it (have to use kill 9) and it's fixed, but what if i'm not there or i don't notice? :/

I don't know much about debug/debugging weechat, so please if you need some reports or something tell me. Also, this doesn't happen all the time, so it'll be a little hard to reproduce i guess.

If it helps, i did nothing fancy with my laptop, just turn it ON, close weechat, ncmpcpp and htop terminal windows (as they open on startup), and then i left the laptop like that. I didn't open anything or used any app.

Version: 1.8
Plugins activated: iset, highmon, autosort

@weechatter weechatter added the bug Unexpected problem or unintended behavior label Jun 3, 2017
@flashcode flashcode added this to the 1.9 milestone Jun 3, 2017
@flashcode
Copy link
Member

It should be fixed, if you can, please try the latest development version and tell me if it's OK now.
To reproduce, just closing the terminal on the secure password prompt should be enough to cause the infinite loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants