moolticute
moolticute copied to clipboard
mooltipass
macOS - the app crash randomly
Expected behavior
The app doesn't crash
Actual behavior
Sometimes, after a while, the application crash.
Step by step guide to reproduce the problem
I don't have any steps, I just use the computer like every day, and the more time I spend without rebooting the more likely moolticute might crash.
Moolticute Version
0.53.7
Operating System
Mention if you are using either:
- MacOS
Mooltipass Device
- The Mooltipass Mini BLE
attaching the error mac displayed me when the app crashed:
damn.... we're about to migrate to qt 6.2.. hopefully this migration should fix that.
I don't know if this is the same thing, but what I'm seeing is that after the first couple of launches of moolticute, further launch attempts are no-ops. I.e. no window pops up. Also, the toolbar icon vanishes, although it might be there but hidden under the camera cutout -- this bites some other apps as well. What's weird is that a ps shows moolticute is in fact running:
: [email protected]:/Users/lyndon/hush/pws; ps -efww|grep -i moolti
: [email protected]:/Users/lyndon/hush/pws; 8 /Applications/Moolticute.app/Contents/MacOS/moolticute
502 8623 8621 0 9:41pm ?? 0:01.52 /Applications/Moolticute.app/Contents/MacOS/moolticuted
This is on an M1 MacBook Pro running MacOS 12.1.
I've just confirmed that killing off the three mooltipass processes will let me re-launch the app. This is version 0.53.7 BTW. I have the log window open now so maybe I can catch something in the act. But it would be useful to know where on disk these logs are being written to.
If the window freezes as well with that it's maybe related to https://github.com/mooltipass/moolticute/issues/883 as well
Hello there! We've just released our latest moolticute beta for macOS, compiled with the QT6 framework (it took us a while...). Would you be able to download and install it at https://betas.themooltipass.com/v0.55.10-testing/Moolticute-v0.55.10-testing.dmg and let us know if you still experience this issue?
Can anyone try the beta? I have the exact same issues here and it really spoils the fun with the mooltipass. Or is this outdated and you already got that incorporated into the release? I am on version 1.0.0.1
Well sadly I cannot say it helped. The moolticute app on mac still crashes randomly and the behavior regarding the UI being closed and not opened again is also still there. The thing is that it happens randomly and thus I cannot really be sure if there is anything going on which might be related. Sometimes the UI just won't show up anymore and then I need to restart all processes related to it to get it back. Eg. if I want to access a note or just wonder why the heck it won't log me on to a website etc. Not sure how to better track this error to help.
wow, it has been quite a while since someone reported random crashing on MacOS. does that happen when moolticute is displayed or hidden?
I usually have plenty of windows open. I don't manually hide the moolticute window. It's just sitting somewhere without being visible. And sometimes when I click the taskbar to get the window back in the foreground it won't show. Using systray doesn't help either in those cases and then I have to restart the daemon.
Here's a crash report from just now. I usually didn't get these. I upgraded to the latest version this morning, so I am up to date. Before it would just not come back to the foreground and react to clicks. This is the first crash report I got. crashreport.txt
moolticute_crash.txt I also got a new one (1.0.0.1 though), though I suspect that one's related to the macBooks energy saving mode
Hello @smallouki, @KDederichs I found some very similar crash reports in Qt applicatons on Mac and they are mentioning it happens when Mac wakes up from sleep mode. Is it possible the same is happening in your cases? https://github.com/texstudio-org/texstudio/issues/1894 https://bugreports.qt.io/browse/QTBUG-79944
@deXol In my case more than possible yeah, since I just close the MacBook without turning it off and it happened after opening it back up.
@deXol I don't know for sure. I have my Laptop hooked up on my desk all the time. I don't turn it off or deliberately to sleep. But it probably goes to sleep after some inactivity.
Anyway, the crash report was a first for me. Usually it just won't react to any input any more. As it does right now for example. I have to restart the daemon which sometimes works. Even though I just did that, moolticute still tells me that the device is locked, which is not the case. Unplugging and replugging the device fixes that. But overall it seems the connection to the device seems rather unreliable.