Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Mattermost continuously updates its application menu without need #5088
Comments
|
Hi @kbroulik - we're not very familiar with DBus, were any of the other applications you used built with React? Not sure if that could cause the difference. If there's suggestions you have for what the code should be changed to, we're open to discussing them |
|
We haven't received an update so we'll assume that the problem is fixed or is no longer valid. If you still experience the same problem, try upgrading to the latest version. If the issue persists, reopen this issue with the relevant information and we'd be glad to help you where we can. |
jasonblais
closed this
Jan 30, 2017
ChALkeR
commented
Feb 11, 2017
|
Upstream bugreport: electron/electron#8455 |
ChALkeR
referenced this issue
in electron/electron
Feb 11, 2017
Closed
Globalmenu consumes 100% CPU and does not work #8455
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kbroulik commentedJan 17, 2017
Summary
Mattermost continuously updates its application menu causing DBus spam
Steps to reproduce
Run Mattermost on a platform which supports global menu (like Plasma 5.9 Beta or potentially Unity). Run Mattermost and observe the output of dbus-monitor. (Mattermost version 3.4.1)
Expected behavior
Only when the menu really changes the application signals a change. For simplicity this could also be done when the window gets focused or another conversation is opened.
Observed behavior
Mattermost signals
ItemsPropertiesUpdatedandLayoutUpdatedfor the root menu which in turn will have the global menu service emitAboutToShowon the submenus (this is needed for certain applications like Firefox to work properly) which in turn will do aGetLayoutand then it starts all over again. Mattermost is the only application I noticed to exert this behavior, none of the other applications do and neither does the Chrome browser. See [1] below for dbus-monitor output.Possible fixes
The mattermost code is as follows
As you can see it constantly emits a the
update-menusignal which in turn will dosetApplicationMenuthus eventually signalling a change.[1] snippet from dbus-monitor output (goes on forever)