macOS Big Sur crashes #2274
Comments
|
i have the same issue with random crashes |
|
Hmm, I can't reproduce the crashes with MacOS 11.0.1 and Betaflight configurator 10.7.0 on a VM, which is all that I have at the moment. Somebody with actual Apple hardware will have to see if they can reproduce / fix. |
|
I'm having the same problem. It seems you can eventually get in and make changes but BF crashes or locks up. Update - version 10.7.0 of Betaflight It usually crashes immediately on startup. After a few restarts, it will stay alive. Same with connect - it crashes after connecting and also during many actions. However, I've seen that the changes made are saving to the quad. |
|
Same problem. Betaflight configurator 10.7.0 crashes after macOS update. |
|
Found this line in an nwjs Helper diagnostic report:
The moment this appeared, BFC just locked up and didn't let me do anything anymore. I doubt a full stacktrace would help here, but it looks like it's caused by nw.js not being fully compatible with Big sur yet. So basically what @mikeller said. |
|
There's a possible workaround as I was not able to reproduce the issue anymore after running the following command VScode is suffering from a very similar issue. Someone posted the above (for Vscode though) workaround fixing the issue. |
|
If all of you can confirm this workaround, we can add it to the Mac OS notes while we find a better fix. |
|
@McGiverGim - confirmed. I'm not seeing any more crashing after running that command. |
|
If it matters, what I see in internet is that some parts of our nw framework have it's own signature, that is invalid. The above command removes them. The perfect solution will be replace this signature by our own, but at this moment we don't have a certificate for that. |
|
@McGiverGim: I guess another way to work around this will be to remove the signature on NW.js as part of the build process. |
|
Good idea. I don't have a Mac to test it. |
|
After having upgraded to macOS Big Sur, my VS Code C++ compiler stopped working. I can not run any of my recent or old projects and files. The problem occurs every time I try to Run Build Task or just Run. I attached some images for easier comprehension, sorry if I didn't explain it well, I'm just a beginner :D
|
I still have random crashes after this command. |
|
Actually, nwjs still runs even after the configurator crashes or gets closed:
|
|
@sael17: This is an entirely unrelated problem, and not pertaining to configurator at all. Please open a new issue at https://github.com/betaflight/betaflight/issues. |
|
Betaflight Configurator is also unstable on an M1 MacBook Air (it can crash on opening, closing or when running, but is still usable some of the time). As it's running Big Sur it could be the same problem and could be NW.js related. Kiss GUI has also crashed with the report showing nwjs. |
|
@AndreaCCIE: Looks like code signing is a red herring - the NW.js apps that we are using are not signed in the first place: |
|
Rebuilding with nw.js version 0.50.1 and node.js 15.3.0, as well as doing |
|
MacBook Air 2019 Big Sur 11.0.1 I am having similar issues however when going into the Setup tab I get this graphic and the program locks up. |
|
Even after doing what @Autocrit said, i still get random crashes :/ MacBook Pro M1 Big Sur |
|
MacBook Pro (Retina, 13-inch, Early 2015)
|
|
Hello, I get this error when running configurator. |
|
@SebastianKumo: This is normal if you used a development version of configurator, and then switched back to the stable version running on an older version of NW.js. Delete your NW.js application settings at |
|
@mikeller the newest master with updated NW.js works for me on macOS big sur without crashes or any other glitches I experienced on 10.7.0 |
|
Thanks @SebastianKumor for the feedback! |
|
@mikeller just had a friend with M1 chip mac confirm that the fix works on M1 big sur mac as well |
|
Thanks! Its working perfectly again. |
|
Hello @mikeller is the new version with nwjs update available as a built binary or do I need to build it? Thanks! Right now on my M1 Mac I get crashes and nwjs is using 200% CPU in a left over zombie process after the crash. I assume the merge you did is related. |
|
Yes biliion (in dutch terms) F405 is still topping but this is big number I did not expect either as we have about 591K active users in last week. In development I flash multiple times within an hour. Should compare OSX and behavior with Windows and Linux. Also want to mention https://web.dev/serial/ . |
|
@barts83eu: Looks like the version of NW.js that we are using might not be stable yet on M1 - we might want to look into updating to a newer version before the next release, if one can be found that works with the libraries used by us. |
|
@barts83eu: Hopefully the problems on M1 Macs should be fixed with #2507. |
|
I am saving for a new apple computer. M1 is half a year old. So when I'm done saving should an M2 be available? |
|
I'm on an M1 with not-quite-latest macOS ( |
|
@kevinsumner Could you please test with latest artifact here: https://dev.azure.com/Betaflight/Betaflight%20Nightlies/_build/results?buildId=3387&view=artifacts&pathAsName=false&type=publishedArtifacts |
|
@haslinghuis just tried v20210802.3387 -- similar results as v20210801.3383, generally good. Using a spare flight controller, I browsed through the configuration tabs and changed a few settings to exercise the build. Only obvious issue I've seen on the v20210802.3387 build is Notification Center entry shows up as nwjs instead of Betaflight Configurator. This looks like a regression from the v20210801.3383 build. I wouldn't expect this to be M1-specific, though. |
|
Thanks for testing! |
|
With v20210802.3387 (bad): |
|
I can spin a build with 0.54.1 if you like to test? You can use the same URL above to get it. |
|
Yup, I can do that! |
|
v20210803.3405 seems to fix the Notifications regression while also maintaining stability. |
|
I can confirm I also had same issue with 105% CPU process nwjs after betaflight crash. I didn't even realized that something wrong until start noticing that laptop is always hot and battery dies out significantly faster than usual. MacbookAir m1 OSX 11.4 |
|
@lebed2045 have you tried a recent nightly build or is that behavior on the current "stable" release? |
|
latest stable release from https://github.com/betaflight/betaflight-configurator/releases/tag/10.7.0 |
|
Same issue here on Big Sur 11.4 (20F71). Sometimes doesn't even open at all. The nightly doesn't crash, but minimizes to the dock when switching spaces 😅 |
|
hello betaflight configurator crash on Mac os monterey. Translated Report (Full Report Below)Process: nwjs [1493] Date/Time: 2021-11-10 10:17:07.7442 +0100 Time Awake Since Boot: 1700 seconds System Integrity Protection: enabled Crashed Thread: 2 StackSamplingProfiler Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0 is not in any region. Bytes before following region: 4299423744 Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread Thread 1:: com.apple.rosetta.exceptionserver Thread 2 Crashed:: StackSamplingProfiler Thread 3: Thread 4: Thread 5: Thread 6: Thread 7:: ThreadPoolServiceThread Thread 8:: ThreadPoolForegroundWorker Thread 9:: ThreadPoolBackgroundWorker Thread 10:: ThreadPoolBackgroundWorker Thread 11:: Chrome_IOThread Thread 12:: NetworkConfigWatcher Thread 13:: CrShutdownDetector Thread 14:: NetworkConfigWatcher Thread 15:: ThreadPoolForegroundWorker Thread 16:: ThreadPoolForegroundWorker Thread 17:: ThreadPoolForegroundWorker Thread 18:: ThreadPoolForegroundWorker Thread 19:: CompositorTileWorker1 Thread 20:: ThreadPoolSingleThreadForegroundBlocking0 Thread 21:: CacheThread_BlockFile Thread 22:: BrowserWatchdog Thread 23:: ThreadPoolSingleThreadSharedBackgroundBlocking1 Thread 24:: ThreadPoolSingleThreadSharedForegroundBlocking2 Thread 25:: Chrome_HistoryThread Thread 26: Thread 27:: NetworkConfigWatcher Thread 28:: Startup watchdog thread Watchdog Thread 29:: com.apple.NSEventThread Thread 2 crashed with X86 Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"nwjs","timestamp":"2021-11-10 10:17:08.00 +0100","app_version":"Version 10.7.1","slice_uuid":"757802d8-a86d-31ab-9ed6-3a951ca13cf6","build_version":"10.7.1","platform":1,"bundleID":"com.nw-builder.betaflight-configurator","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.0.1 (21A559)","incident_id":"0D6287B8-F7B4-453A-989A-6C5DAA3A2BFD","name":"nwjs"} ], ] Model: MacBookPro17,1, BootROM 7429.41.5, proc 8:4:4 processors, 8 GB, SMC |
|
Confirmed it's working now with v10,8,0 on M1 (using NW.js 054.1) |
|
would like to build a 10.4.0 version of configurator for use on a pre-M1 Macbook and having trouble finding/understanding the fix for the original bug here macOS Big Sur, the configurator is very unstable. much appreciated if someone can point me in the right direction, thanks. |
- see: betaflight#2274 - bump NW.js to v50.2 to fix MacOS Big Sur instability - change status string to "Configurator (NW.js v50.2) " - also supress check for newer version of configurator
and others
Describe your problem;
After having upgraded to macOS Big Sur, the configurator is very unstable.
Is does crash often while on the PIDs tab, but it happens even on other tabs
Include ways to reproduce the problem;
Open the configurator, go to the PIDs tab and play with sliders/drop down
Provide as much information as possible about your hardware and software, including:
what hardware / software you are using;
MacBook Pro 13 2018 (irrelevant)
the version of all the software used;
macOS Big Sur 20B29
Betaflight Configurator both stable 10.7.0 and 10.8.0 v202011041226
The text was updated successfully, but these errors were encountered: