Stats 2.4.0 crashes after each app restart

[jgoldhammer]

Stats 2.4.0 crashes for me. After a restart, stats crashes every time. I have attached a crash report...

Stats_2020-11-02-084010.txt

[wfrank21]

16:04 CET seems to work fine, but only one row mode works

[exelban]

Could you try this one with the disabled Fans module and enabled Sensors? Stats.dmg.zip

[Coliinnn]

16:04 when the fans module is enabled it shows just an empty space in the menubar for two row. . No crash though. Single row displays it the right way

[exelban]

[16:04] This version works because it has disabled rendering the 2 rows.

[entee55]

16:04 CET works for me but no sensor readings. It only shows blank

[exelban]

Yeap, it works and shows blank because it has disabled rendering (which is the crashing reason).

[exelban]

Stats.dmg.zip

[Coliinnn]

16:17 with fans disabled and two-row sensor heatpipe readings enabled does not crash for me it seems. Update: I think it did crash after a while

[exelban]

Ok, it looks like we need to select some testing method. Could you please turn on the Sensors and Fans module?

Stats.dmg.zip

[Coliinnn]

16:36 crashed when I had both sensors and fans double row. But the previous build from 16:17 also crashed after a while with two row sensors, no fans.

[entee55]

16:36 same for me. Crashed if sensors and fan enabled with 2 row.

[exelban]

Ok, I revert the changes of this widget. Could you test it? Stats.dmg.zip

[Coliinnn]

16:49 crash with both two-row sensor and fans. Two-row sensors (no fans) crashed, two-row fans crashed too. :(

[entee55]

seems goods far. no crash for 4 minutes. Fan and sensors enabled. 2row option is not there, but working as expected.I only have one fan, so maybe that's the key point for the crash.

[exelban]

@Coliinnn Ok, so it looks like the Fans module is not causing the problem. The problem is with the widget itself. @entee55 the last version works fine for you? No crashes?

[entee55]

yes no crashes yet. for 10 minutes

[Coliinnn]

@entee55 do you have two-row sensors or one? And sometimes when it doesn't crash for me, when I click on the module it then crashes still. @exelban yes it seems like it, it happens on both modules

[entee55]

2 row sensors, I clicked on it and no crash. But the 2 row sensors is now automatic, no option to select 2 row

[entee55]

oh, it just crashed after 12 minutes

[exelban]

Stats.dmg.zip

[entee55]

should it remember my earlier settings? every new file you send have sensors and fan set on, like before removing the older version

[exelban]

Better to have Sensors and Fans modules on

[entee55]

yeah sure. I was only asking because I read earlier that by default both are off. I thought maybe it was important.

[exelban]

It disabled by default. But it causes crashing. So it must be turned on.

[exelban]

What about the last build?

[entee55]

no crashes so far. Running for 8 minutes. I tried to click every module, no crash yet.

[exelban]

Ok. Thanks. Could you try this one? Stats.dmg.zip

[exelban]

If the app not crashing on launch, it will not crash with time. It can crash with time only in these builds because I just try to prevent crashing.

[entee55]

no crash. 2 row option is back

[entee55]

it crashed after 3 minutes

[exelban]

Nice, nice. What about this one? Could you send a crash report?

Stats.dmg.zip

[Coliinnn]

17:15 you can see the 'RPM' text does not fully render, it only shows part of the R. But no crash at start

[Coliinnn]

17:31 The RPM text renders fully again, no crash at start yet. Both modules turned on with two-row. I will let it run for a bit

[entee55]

17:31 same for me

[entee55]

it just crashed

[entee55]

sorry, I do not know how to send a crash report

[exelban]

No problem. In the Utilities folder find an app called Console. Open it and you will see in the left part tab called Reports. There you can find all reports of crashed apps. Or you can do it with a spotlight, just search console.app.

Could you check this one? Stats.dmg.zip

[entee55]

earlier crash report. now testing the new Crash report 1735.txt

[entee55]

latest crash report Crash report 1756.txt

[exelban]

Don't post a crash report every time. It will be the same) So, it not crash at the start. But with some time?

[Coliinnn]

The 17:31 did not end up crashing for me. 17:44 crashed after 1-2 minutes. Not immediately at the start. No crash report needed this time?

[exelban]

Nope. Thanks.

[entee55]

it crashed about after half a minute

[exelban]

Ok. What about this one? I hope it will work without crashes. But yeap, the width of the widget (sensors and fans) will be strange.

Stats.dmg.zip

[entee55]

no crash at start. crashed after 2 minutes. fan rendering failure: only shows first 2.5 characters of actual speed

[Coliinnn]

Three minutes, no crash yet

[exelban]

Stats.dmg.zip

[entee55]

crash at start. rendering was OK though actually crash was at first click second run: crashed without click after 10 sec.

[exelban]

I just cannot understand what happens. How it possible that the app crashing after some time( It just update the value, but in some moment crashing with the reason that some sensor is no allocated(

[Coliinnn]

No crash at start for me actually, also not when clicking it. Took about 50 seconds, then crashed