-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
V3.0.2 keeps crashing [bug] #988
Comments
Seeing this crashing still on my end as well. I've had to switch to another scroll wheel reverser for the time being as it's nearly unusable. 😢 |
I bought the license but the crashes are so constant that its unusable. With one are you using? |
Given that this is a support forum for a product, I'm going to refrain from mentioning competitors, but there are absolutely other mouse wheel reversers in the market at the moment. |
Been testing for a while, so far no crashes. Will update if crashes persist, thanks! edit: so, unfortunately the crashes persist with vcoba-2, but it is more stable and the crashes happen less often. I'd say it is usable, but far from ideal. edit 2: the standard vcoba (not the vcoba-2) is solid, working flawlessly until now, will test further and update if there are any crashes. |
vcoba2 seems to work well for me. |
which disables asserts for non-release builds. -> In 3.0.2, asserts were enabled the whole time, which contributed to a crash on ``` assert(tick <= _scrollConfig.consecutiveScrollTickIntervalMax); ``` inside Scroll.m. (See: #988) - We also made some other slight adjustments to make the NDEBUG flag work (added exit(1) and returns in some places where before we only used assert(false)) - We also improved logging inside AccessibilityCheck.m - Very slight doc improvements TODO: - Figure out how exactly the assert that caused #988 could become false
Hey guys, thanks for your feedback! I'm currently looking into this. I looked at the crash report and it seems the crash comes from this line of code according to my symbolication. I've never ever seen this on my computer, and I'm just studying the code but it's really weird that this happens. Especially that you report "constant crashes", when I've never encountered this is strange. I also don't understand why this would only happen on the v-coba builds. I'm building some workarounds so the app can recover when it gets into this weird state, but hopefully I can figure out more. |
Also I have some questions, that might help get to the bottom of this:
If someone else with the issue can share their crash reports that would also be really interesting. The one from @Lajota1 has already been very helpful. |
Oh and if you guys want I'd like to give anyone affected by this a refund. Just shoot me an email. |
@noah-nuebling to clarify, the crashing doesn't occur on vcoba builds for me. You should also have crash logs submitted by me from April 2, 2024. |
Hey @plttn, thanks for getting back. That's interesting that you don't have the issue on the I looked at your crash report and it's consistent with the one that @Lajota1 shared. So that's also very helpful. |
To answer the questions:
Never
As far as I'm aware no, (also because my Mac is a 64 gig of RAM model)
M1 Max 2TB/64GB
Just scrolling is enough to cause it to crash. |
@plttn thanks for getting back! Are you guys using the |
I'm using |
@plttn oh that's very interesting! From my understanding so far, I thought the crash happens inside code that is only executed when using |
As far as I know I've been using smoothness high since it released. |
….0.2 scrolling crashes described in #988. Also did minimal cleanup, logging improvements, and doc improvements.
Same issue here, definitely using Smoothness High (and Trackpad Simulation, macOS speed, inverse direction). I'm on M3 Pro. The issue started happening yesterday out of the blue, I haven't had anything alike since I started using Mac Mouse Fix (still in the v2 era). I sometimes use SHIFT-scrolling, but it is not required to trigger the bug. I see you pushed workarounds to recover from the bug - any idea when you might release it? Thanks! |
@noah-nuebling any plans to release a non-beta version with these fixes yet? I've been stuck on 3.0.2-vcoba2 since my initial crash reports. |
Hey guys, I plan to release a fix tonight or tomorrow with the 3.0.3 release! I was working on improving the localization system across the project, and I sort of got tunnel-visioned on that. I'm really sorry it took me so long to address this. I've never experienced this crash even though I tried to reproduce it to catch it in the debugger for a while. And I'm still not sure what could lead to the internal conditions in the app that caused the crash. But if those conditions occur, the app should smoothly recover under 3.0.3 instead of crashing. For now, the workaround in 3.0.3 should work ok, but if I want to work on the scrolling system in the future, it might be really valuable to understand this better. If anybody's still experiencing these crashes (or if you did still experience them when you were last using 3.0.2) it would be really valuable if you sent your The config.plist file holds pretty much all settings and state that is retained between launches of the app. You can find it like this:
Thank you, for your help. |
Thanks for the update! Is there any chance a macOS bug or odd behaviour could be contributing? I cannot reproduce the issue on macOS 15.1 Beta 4 right now (on 3.0.2 of course). |
@mhaeuser That's an definitely a possibility that I hadn't considered before. It would be very interesting to hear whether you start seeing the crashes again, or whether it stays crash-free under 15.1. |
I experienced crashes on 3.0.2, so here's my config.plist. |
@mxalbert1996 I can't spot anything weird with that config.plist file after a quick check, but I'll use it with 3.0.2 for a while to see if I might be able to reproduce the crashes. Thanks very much! |
Description
So MMF V3.0.2 keeps crashing and getting back all the time, mainly when a use the scroll wheel a lot. The app will stop working and the icon at the top will disappear, a few seconds later it will reappear and start to work again. Sonoma 14.5.
Steps to reproduce
1- Use the scroll wheel a lot
Context
Mac Mouse Fix Version: 3.0.2
macOS Version: Sonoma 14.5
Mouse Model: Viper V2 Pro
Additional Comments
–
Console Logs
void _updateToReflectAutomaticTerminationState(void) Setting _kLSApplicationWouldBeTerminatedByTALKey=1
Crash Reports
https://pastebin.com/YeeVjKZz
The text was updated successfully, but these errors were encountered: