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

Cube leaks memory every time it's activated #2059

Closed
lcolitti opened this issue Dec 8, 2023 · 0 comments · Fixed by #2060
Closed

Cube leaks memory every time it's activated #2059

lcolitti opened this issue Dec 8, 2023 · 0 comments · Fixed by #2060
Labels
bug

Comments

@lcolitti
Copy link
Contributor

lcolitti commented Dec 8, 2023

Describe the bug
When using cube, the wayfire process leaks several MB of shared memory every time the cube is activated.

To Reproduce
Steps to reproduce the behavior:

  1. Enable cube
  2. Run "watch -n0.1 ps u -p $(pidof wayfire)" and "watch -n0.1 free -m"
  3. Activate cube
  4. Observe memory usage going up.

Expected behavior
No memory leak.

Wayfire version
0.8.0 and git
@lcolitti lcolitti added the bug label Dec 8, 2023
lcolitti added a commit to lcolitti/wayfire that referenced this issue Dec 8, 2023
@lcolitti
cube: release framebuffers on deactivate
ddeb985 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
lcolitti added a commit to lcolitti/wayfire that referenced this issue Dec 8, 2023
@lcolitti
cube: release framebuffers on deactivate
908f3cd 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
@lcolitti lcolitti mentioned this issue Dec 8, 2023
Merged
lcolitti added a commit to lcolitti/wayfire that referenced this issue Dec 8, 2023
@lcolitti
cube: release framebuffers on deactivate
e638a73 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
lcolitti added a commit to lcolitti/wayfire that referenced this issue Dec 8, 2023
@lcolitti
cube: release framebuffers on deactivate
d9a9a88 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
lcolitti added a commit to lcolitti/wayfire that referenced this issue Dec 11, 2023
@lcolitti
cube: release framebuffers on deactivate
8d1cd34 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
ammen99 pushed a commit that referenced this issue Dec 20, 2023
@lcolitti
cube: release framebuffers on deactivate (#2060)
1643255 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes #2059
mrsteve0924 pushed a commit to mrsteve0924/wayfire that referenced this issue Mar 2, 2024
@lcolitti @mrsteve0924
cube: release framebuffers on deactivate (WayfireWM#2060)
32b54cc 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes WayfireWM#2059
ammen99 pushed a commit that referenced this issue Mar 13, 2024
@lcolitti @ammen99
cube: release framebuffers on deactivate (#2060)
6fcde52 
Currently it looks like the framebuffers are allocated on
activate but never released. This causes a substantial memory
leak. Fix this by adding a destructor to cube_render_instance_t
that releases them.

Fixes #2059
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
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix memory leak when activating cube plugin lcolitti/wayfire
1 participant
@lcolitti