super-wingpanel, global menu, memoryleak
Bug #1275016 reported by
🦇 MΞMØΓЧŁΞΛКX 🐧
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Super Wingpanel |
In Progress
|
High
|
Heath Paddock |
Bug Description
After closing of applications with (app menu), the memory will not released.
Changed in wingpanel: | |
assignee: | nobody → Heath Paddock (heathbar) |
Changed in wingpanel: | |
assignee: | Heath Paddock (heathbar) → Francisco Javier Delgado del Hoyo (frandelhoyo) |
assignee: | Francisco Javier Delgado del Hoyo (frandelhoyo) → nobody |
assignee: | nobody → Heath Paddock (heathbar) |
Changed in wingpanel: | |
status: | New → In Progress |
affects: | wingpanel → super-wingpanel |
Changed in super-wingpanel: | |
importance: | Undecided → High |
To post a comment you must log in.
Note: when one sweitches between applications there is a brief spike in processor usage for wingpanel. However, the RAM usage of wingpanel only grows up from 10M if one keeps clicking on the menus/submenus - i.e. File>submenus, Edit->submenus, and all the other ones too. Where one ends up with wingpanel being ~40M of unflushed (cached menus?) stuff.