-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Crushing #341
Comments
Can't reproduce on my machine. Please run |
|
Hard to tell, what's going on. Please try to run with debug messages: |
okay here it is, i appreciate your feedback. |
** (com.github.stsdc.monitor:22383): CRITICAL **: 15:26:58.096: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:01.092: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:04.042: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:07.097: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:10.094: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:13.105: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:16.102: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:19.094: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:22.106: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:25.040: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:22383): CRITICAL **: 15:27:28.041: monitor_igpu_get_percentage: assertion 'self != NULL' failed |
and another one |
** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:33.470: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:36.461: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:39.456: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:42.465: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:45.464: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:48.507: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:51.386: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:54.386: monitor_igpu_get_percentage: assertion 'self != NULL' failed ** (com.github.stsdc.monitor:27169): CRITICAL **: 16:51:57.386: monitor_igpu_get_percentage: assertion 'self != NULL' failed |
Released an update. Please check it. |
updated still crashing |
Monitor is also crashing for me regularly right now. My system (NixOS 22.11.2179.0218941ea68) is in the state that the CPU is 100% used because 2 Nix builds seem to have a deadlock (NixOS/nixpkgs#217247). I'm still running Monitor 0.14.0. Will teste the update.
I have many coredumps, but the backtrace is always identical.
|
I gave up, wanna find another alternative that can check my system on the status bar |
@issar13 check this alternative https://github.com/PlugaruT/wingpanel-monitor |
@issar13 i don't know how relevant this information still is, but here are other options: https://elementaryos.stackexchange.com/questions/611/how-to-display-cpu-temperature-in-wingpanel But i hope we can resolve this issue. |
The issue i had seem to be fixed by the update to the latest version. So i guess we can close this. |
New Bug it keeps on crashing once CPU reaches 100%
The text was updated successfully, but these errors were encountered: