Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Openbox leaking memory? (Read 2145 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: [SOLVED] Openbox leaking memory?

Reply #30 –
Quote from: lieangeofruits – on
Hi everyone. I have solved this issue (as good as it gets for now).
......

Let me know if it works out for you guys.

Thanks
I'll give this a try. I have already patched a few places where NULL has been seen in tint2. I will try your fix as well.

Re: [SOLVED] Openbox leaking memory?

Reply #31 –
Quote from: replabrobin – on
Quote from: lieangeofruits – on
Hi everyone. I have solved this issue (as good as it gets for now).
......

Let me know if it works out for you guys.

Thanks
I'll give this a try. I have already patched a few places where NULL has been seen in tint2. I will try your fix as well.

One of the Devs on GitHub also suggested an alternative solution that might work as well
" you can build conky with BUILD_XINPUT disabled (cmake -D BUILD_MOUSE_EVENTS=OFF) which will disable related event code in conky."

I can confirm that my fix of tint2 works on several window managers that I have tested (Will probably work on any window manager). It's not the most efficient/elegant solution, but it's a hack that works.
 

Re: Openbox leaking memory?

Reply #32 –
So, it seems there has been some confusion in this thread and it was marked as "Solved" erroneously.

This thread has begun with an issue specifically involving the interaction between Conky and OpenBox (Tint2 has been put out of the equation in my tests, since I used only startx and openbox, without starting Tint2).

It seems that with my issue, another issue (in the same release of Conky) has appeared that made Tint2 crash. (In hindsight, a dedicated thread would have been better). I think it's better to leave Tint2 aside or the thread may become really messy.

There is a patch upstream, as mentioned in the Conky repo issue https://github.com/brndnmtthws/conky/issues/1771, which should stop propagating messages that are not strictly related to input events.

I haven't tested this patch yet, thus I think marking this thread as "solved" is a bit premature.

Re: Openbox leaking memory?

Reply #33 –
Quote from: Penaz – on
So, it seems there has been some confusion in this thread and it was marked as "Solved" erroneously.

This thread has begun with an issue specifically involving the interaction between Conky and OpenBox (Tint2 has been put out of the equation in my tests, since I used only startx and openbox, without starting Tint2).

.....

Yes, in hindsight this thread got a bit confusing. I ended up here though a google search because I wanted to post my fix for tint2 to anyone experiencing the problem. I did not see the whole thread or the topic lol.
I just saw the bits about tint2 and conky.

Well at least one issue is solved now.
Please do try my fix of tint2. It will stop tint2 from crashing when hovering or clicking on conky


Also have you tried this fix?  " you can build conky with BUILD_XINPUT disabled (cmake -D BUILD_MOUSE_EVENTS=OFF) which will disable related event code in conky." ~ Github conky issue

I don't know what else is happening with openbox and conky, but disabling input events for conky (which is normally doesnt need anyway) seems like a good idea.
It does seem like Conky was causing problems by forwarding events and what not,  some changes have been made to conky source regarding input events so perhaps installing conky from git again will solve your openbox issues. Particularly building it without Mouse events.








Re: Openbox leaking memory?

Reply #34 –
Update: There's a New Tint2 package in the Arch and Artix repos now. Tint2 doesn't crash with conky anymore.

Re: Openbox leaking memory?

Reply #36 –
I've been testing the git version of Conky for a couple days and it seems the patch solves both the Tint2 crashing and OpenBox memory issues.

The Tint2 patch will make doubly sure that the panel doesn't crash, which is always a good thing.

I think we can mark this thread as solved, since we just need to wait for a new release of Conky.

Thank you everyone for your patience and help.

Re: Openbox leaking memory?

Reply #37 –
You might have to update conky from git one more time. There's another small tweak with event propagation in there.
Other than that, it's all solved.

The thought of changing your entire Desktop setup from openbox, conky, tint2  must have been a dark prospect, i've been there.
It's always hard having to change your usual flow.