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.

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

Crash on sleep #1969

Open
gorans opened this issue May 27, 2024 · 43 comments
Open

Crash on sleep #1969

gorans opened this issue May 27, 2024 · 43 comments
Labels
bug Something isn't working

Comments

@gorans
Copy link

gorans commented May 27, 2024

I noticed couple of times that Stats is no longer active after waking from (deep) sleep. Checked logs and there were several crash logs that I think correspondent with entering sleep. I attached the last one.

MacOS 12.7.5
Stats 2.10.15
stats crash log.txt

@exelban
Copy link
Owner

exelban commented May 27, 2024

It's a bug in macOS. You need to disable monospaced font or static size for the Stack widget if it's enabled.

@gorans
Copy link
Author

gorans commented May 27, 2024

I don't have Stack widget. I also don't have monospaced font or static width enabled in any widget.
I had combined modules enabled. I disabled it now and will monitor if anything changes.

@exelban
Copy link
Owner

exelban commented May 27, 2024

please share what the widgets look like. Because the crash report says that it crashes when trying to show that widget.

@gorans
Copy link
Author

gorans commented May 27, 2024

Here are all widgets that I use:
Screenshot 2024-05-27 at 17 49 24
Screenshot 2024-05-27 at 17 49 54
Screenshot 2024-05-27 at 17 50 28
Screenshot 2024-05-27 at 17 49 45
Screenshot 2024-05-27 at 17 50 09

@exelban
Copy link
Owner

exelban commented May 27, 2024

thx, it's a sensors widget. Please share the setting that you have for that widget in the Sensors module.

@gorans
Copy link
Author

gorans commented May 27, 2024

There You go:
Screenshot 2024-05-27 at 20 27 12

@exelban
Copy link
Owner

exelban commented May 28, 2024

hmm, interesting. Will check that.

@gorans
Copy link
Author

gorans commented May 28, 2024

Just for test, I turned "Combined modules" back on and had another crash.

@exelban
Copy link
Owner

exelban commented May 28, 2024

So if combined modules is off there are no crashes?

@gorans
Copy link
Author

gorans commented May 28, 2024

It seems so.. :)

@exelban
Copy link
Owner

exelban commented May 28, 2024

hmm, strange

@ryadom
Copy link

ryadom commented May 28, 2024

Same for me. I also using combined module.

Stats-2024-05-27-153617.txt

@svkirillov
Copy link

I have the same issue. I use GPU, CPU, RAM, Sensors (stack, defaults), and Network modules. Modules are combined, details are not combined.

stats-crash-log.txt

@exelban
Copy link
Owner

exelban commented Jun 3, 2024

Please try this build

Stats.dmg.zip

@exelban exelban added the bug Something isn't working label Jun 3, 2024
@gorans
Copy link
Author

gorans commented Jun 3, 2024

I don't know what was this crash, but report attached.
I just put machine to sleep and wake it up and Stats still running with posted build.

crash.txt.zip

@exelban
Copy link
Owner

exelban commented Jun 3, 2024

thx. Please try this one:

Stats.dmg.zip

@gorans
Copy link
Author

gorans commented Jun 3, 2024

So far so good. :)

@exelban
Copy link
Owner

exelban commented Jun 3, 2024

ok, please try this one:

Stats.dmg.zip

@gorans
Copy link
Author

gorans commented Jun 5, 2024

No crashes since v2.10.15, latest from here.
Thanks!

@exelban
Copy link
Owner

exelban commented Jun 5, 2024

hmm, interesting.

@exelban
Copy link
Owner

exelban commented Jun 5, 2024

try this one please:

Stats.dmg.zip

@kuba2kopec
Copy link

I've recently noticed the same issue. In my case, Stats was installed via homebrew, and today, after I found this thread, I overwrote it with the build you sent above. I'll monitor the situation and let you know if it crashes again :)

@gorans
Copy link
Author

gorans commented Jun 8, 2024

I had another crash. Report attached.

stats_crash.txt.zip

@exelban
Copy link
Owner

exelban commented Jun 8, 2024

hi. thx.
Please download the release version of the Stats, and enable the static width option in the sensors widget.

@gorans
Copy link
Author

gorans commented Jun 9, 2024

Crash with release version.
crash.txt.zip

@exelban
Copy link
Owner

exelban commented Jun 9, 2024

do you have enabled static width?

@gorans
Copy link
Author

gorans commented Jun 9, 2024

Yes.
Screenshot 2024-06-10 at 03 08 41

@exelban
Copy link
Owner

exelban commented Jun 10, 2024

could you please run the latest release?
and share the report, I do not have links for the build you shared crash from(

@gorans
Copy link
Author

gorans commented Jun 11, 2024

Another crash with newest version:
crash.txt.zip

@kuba2kopec
Copy link

kuba2kopec commented Jun 11, 2024

Just had a crash with the latest build sent by @exelban in this thread:
Stats-2024-06-10-230434.txt.zip

@exelban
Copy link
Owner

exelban commented Jun 11, 2024

thx, I cannot understand why it crashes.

Could someone please try to do the following:

  • disable all modules except CPU
  • check if there is a crash
  • enable the next module
  • check if there is a crash
    ... end repeat that for each next module till a crash appears.

@gorans
Copy link
Author

gorans commented Jun 11, 2024

I'll try to do that but it'll take time as I don't know what triggers the crash.
Do You want any fixed settings besides "static width" in widgets?

@exelban
Copy link
Owner

exelban commented Jun 11, 2024

the problem is here:

Zrzut ekranu 2024-06-11 o 21 55 28

So when static width is enabled there must be no crash, because this line must not be triggered. But if it does not help I need to know what calling that line is. I have no idea what it could be since it's a widget drawing.

@kuba2kopec
Copy link

That's interesting, because for me the crash was happening with the following widgets enabled:
image
I don't see the "static width" setting in any of these. Is it possible that the problematic code still triggered?

@exelban
Copy link
Owner

exelban commented Jun 13, 2024

And it's strange. Because it must not be triggered. And according to the @gorans it's triggering even when cannot be.
So I'm wondering why.

@kuba2kopec
Copy link

Had another crash. I don't think that anything other than Stats version (now it's 2.10.17) changed. I haven't disabled any modules yet
Stats-2024-06-16-170900.txt

@kuba2kopec
Copy link

kuba2kopec commented Jun 16, 2024

Actually I found something interesting. That's how the stack widget looks for me:
image
I'm not sure why that is the case

@exelban
Copy link
Owner

exelban commented Jun 16, 2024

it's because you don't have any sensors enabled

@kuba2kopec
Copy link

oh, right. Weirdly I don't see the option to enable any in the settings. Not big deal for me since I don't use this widget, but I found this a bit interesting.

What I did was to enable static width and then hide the widget again. My thinking is that now, even though hidden, the static width is enabled so maybe the problematic code won't trigger

@kuba2kopec
Copy link

So it didn't help, another crash happened:

Stats-2024-06-17-173900.txt

@exelban
Copy link
Owner

exelban commented Jun 18, 2024

@kuba2kopec even with only CPU module enabled?

@kuba2kopec
Copy link

I'll check that, the last crash was with CPU, GPU, sensors and network. But I can't figure out what exactly triggers the crash - sometimes my computer will go to sleep and nothing crashes

@kuba2kopec
Copy link

Now I've disabled everything except CPU and we'll see what happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Progress
Development

No branches or pull requests

5 participants