App continually crashes in macOS. Annoyingly I’m not sure how to reproduce it. Sometimes it’s while I’m actively typing a note. Other times it seems to crash as soon after opening it when I try to drag it from one monitor to another. I’ll update if I figure out better repro steps but it’s crashing at least 10 times a day right now and wanted to let you know.
Hi Stefan,
Thanks for reporting.
That sounds strange. I haven’t been experiencing app crashes on my mac.
Do you remember when it starts crashing? Has it been working fine before?
Maybe it occurs in the main process, so can you try enabling logging? See the docs:
You may get some errors when the app crashes.
Do you remember when it starts crashing? Has it been working fine before?
It was working fine before. To be honest I can’t remember a crash before recently. It seems to have started during 5.9.x. I remember when 5.10 came out and I was hoping there’d be a note about crashes being addressed so it must have started before then so I’d say 5.9.x.
Finally got a couple crashes today after starting logging.
Here’s the end of the log when it crashed. I see the logging is mostly full of that “Missing attribute name” message.
[97118:0317/104853.167401:INFO:CONSOLE(2453)] "Missing attribute name 'data-index={index}' on measured element.", source: /Applications/Inkdrop.app/Contents/Resources/node_modules/@bugsnag/browser/dist/bugsnag.js (2453)
[97118:0317/104853.167426:INFO:CONSOLE(2453)] "Missing attribute name 'data-index={index}' on measured element.", source: /Applications/Inkdrop.app/Contents/Resources/node_modules/@bugsnag/browser/dist/bugsnag.js (2453)
[97118:0317/104853.167452:INFO:CONSOLE(2453)] "Missing attribute name 'data-index={index}' on measured element.", source: /Applications/Inkdrop.app/Contents/Resources/node_modules/@bugsnag/browser/dist/bugsnag.js (2453)
[1] 97118 trace trap /Applications/Inkdrop.app/Contents/MacOS/Inkdrop --enable-logging
I saw some other messages in the logs before one of the crashes but not the other crash so I think it’s unrelated. Here it is anyway just in case:
[36342:0317/101641.121181:WARNING:codec.cc(515)] Explicitly added H264 constrained baseline to list of supported formats.
[97118:0317/101641.336738:INFO:CONSOLE(2)] "Client Token is not configured, we will not send any data.", source: https://d1a7p14oqam61r.cloudfront.net/packs/vendors~checkout~confirmation~dashboard~home~login~main~onboarding~post_sso~registration~replay~unlock~waiting_room-f08c33b5319ea3788c18.js (2)
[97118:0317/101641.560702:INFO:CONSOLE(1)] "Creating new AudioContext", source: https://d1a7p14oqam61r.cloudfront.net/packs/vendors~checkout~confirmation~dashboard~login~main~onboarding~post_sso~registration~replay~unlock~waiting_room-06355b272d42c840b41d.js (1)
[97118:0317/101642.307763:INFO:CONSOLE(199)] "The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu", source: https://d1a7p14oqam61r.cloudfront.net/packs/main-4dd7dbd080498920d92f.js (199)
[97120:0317/101642.442781:WARNING:angle_platform_impl.cc(49)] SizedMRUCache.h:150 (TrimCache): Overflowed the render pipeline cache limit of 64 elements, removing the least recently used to make room.
[97118:0317/101642.549482:INFO:CONSOLE(1)] "connected - 1224ms", source: https://d1a7p14oqam61r.cloudfront.net/packs/vendors~checkout~confirmation~dashboard~login~main~onboarding~post_sso~registration~replay~unlock~waiting_room-06355b272d42c840b41d.js (1)
[97118:0317/101643.049279:INFO:CONSOLE(1)] "unexpected console output: ", source: https://d1a7p14oqam61r.cloudfront.net/packs/vendors~checkout~confirmation~dashboard~login~main~onboarding~post_sso~registration~replay~unlock~waiting_room-06355b272d42c840b41d.js (1)
[97120:0317/101643.432711:WARNING:angle_platform_impl.cc(49)] SizedMRUCache.h:150 (TrimCache): Overflowed the metal library cache limit of 64 elements, removing the least recently used to make room.
Thanks for the report.
Didn’t you get any stack trace in the console? 
hmm
Regarding the Missing attribute name warnings, they have been fixed in v5.11.0 (currently beta).
I don’t think it can cause such a crash but I hope it will solve it.
The second logs look like from a third-party plugin that uses audio.
As you can see it tries to load js files from https://d1a7p14oqam61r.cloudfront.net/.
Are you aware of it?
It seems to involve native features, so it might have something to do with the crash.
Which plugin is it?
Oh weird looks like that’s Coderpad. It does seem to crash a lot while I’m doing tech interviews while in Zoom and Coderpad at the same time. I’ve tried to reproduce it when not doing them and it doesn’t happen. I’ll look into that possibility.
I will say after having it crash a couple more times during an interview just now it seems to happen during the Sync step. It will either crash when I hit CMD+S to save and see the little “Syncing…” in the corner. Or after it crashes when I reopen Inkdrop I’ll see a blank screen with “Syncing…” in the corner and then it crashes after a bit. It seems to lock up the computer a bit during that Sync step as well.
Sorry I don’t have more specifics but that’s what I got right now.
Well, I’d like to know why my Electron app loads Coderpad’s scripts. Do you know why?
Do you embed a Coderpad widget or something in your notes?
Or, does Coderpad inject scripts into other desktop applications automatically?
If you have another computer, does the crash also happen on it?