Crash on sleep

[gorans]

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]

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

[gorans]

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]

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

[gorans]

Here are all widgets that I use:

[exelban]

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

[gorans]

There You go:

[exelban]

hmm, interesting. Will check that.

[gorans]

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

[exelban]

So if combined modules is off there are no crashes?

[gorans]

It seems so.. :)

[exelban]

hmm, strange

[ryadom]

Same for me. I also using combined module.

Stats-2024-05-27-153617.txt

[svkirillov]

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]

Please try this build

Stats.dmg.zip

[gorans]

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]

thx. Please try this one:

Stats.dmg.zip

[gorans]

So far so good. :)

[exelban]

ok, please try this one:

Stats.dmg.zip

[gorans]

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

[exelban]

hmm, interesting.

[exelban]

try this one please:

Stats.dmg.zip

[kuba2kopec]

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]

I had another crash. Report attached.

stats_crash.txt.zip

[exelban]

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

[gorans]

Crash with release version. crash.txt.zip

[exelban]

do you have enabled static width?

[gorans]

Yes.

[exelban]

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

[gorans]

Another crash with newest version: crash.txt.zip

[kuba2kopec]

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

[exelban]

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]

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]

the problem is here:

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]

That's interesting, because for me the crash was happening with the following widgets enabled:

I don't see the "static width" setting in any of these. Is it possible that the problematic code still triggered?

[exelban]

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]

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]

Actually I found something interesting. That's how the stack widget looks for me:

I'm not sure why that is the case

[exelban]

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

[kuba2kopec]

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]

So it didn't help, another crash happened:

Stats-2024-06-17-173900.txt

[exelban]

@kuba2kopec even with only CPU module enabled?

[kuba2kopec]

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]

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

[svkirillov]

Got another crash: stats_crash.txt

Modules (combined):

1. Sensors (temp CPU, GPU)
2. CPU
3. GPU
4. RAM
5. Network

[ryadom]

No more crashes with: CPU, GPU, RAM, Battery modules. Combined modules enabled with no spacing. Version: 2.10.17 I will keep adding more modules.

[kuba2kopec]

For me no crashes up to this point with CPU, GPU and Network modules.

Seems like either I'm very lucky or the Sensors module was causing the issue. I'll wait a bit longer and then finally add the sensors module

[exelban]

@kuba2kopec thx for the feedback

[gorans]

I had no crashes with 2.10.18. Just updated to .19. I'm using CPU, RAM, sensors and network widgets, combined.

I consider this bug solved. Thanks. :)

Best regards.

[kuba2kopec]

I just added the sensors widget in 2.11.1. That means I'm back to my original setup of widgets.

Hope @gorans is right saying that the bug is solved. If I have another crash I'll of course let you know ;)

[ryadom]

I've added all widgets (except bluetooth and clock) a few days ago. No more crashes. It seems resolved for me completely. Version: 2.10.17 Thank you!