Sync Version: 3
Profile Version: 44
Keychain Supported: No
Revision: 7d2c1c0
Sync target
Dropbox
What issue do you have?
I had a note that came (along with all my others) from Evernote. It was a huge file of HTML containing a recipe, and I was trying to clean it up in the visual editor and then in Markdown. Then Joplin started crashing with the error message in the title. Now I can't start it without it crashing unless I disable syncing.
I have managed to delete the note, but would like to be able to go back to using Jopling which I was finding to be a huge upgrade on Evernote.
Would you be able to share this HTML note here? As that would be great if we could replicate and fix this crash.
Regarding sync, it's possible that the issue is that one of the resources is too large. Have a look under Tools => Attachments, and sort by size. Then if some of them are particularly large and you don't need them, delete them. Then hopefully sync should work again.
Sadly the note has gone - I managed to delete it thinking that might cure the problem.
I have run the debugging setup - and the application falls over, it seems, due to an out of memory issue - see screen shot. I have updated to Joplin 2.14.17 (prod, darwin), BTW.
I am having the same problem. Same circumstances - I imported many notes from Evernote, now Joplin crashes a minute or two after starting with the "renderer process gone" error. In my case I do not have syncing enabled, so that's not it. I do have some very large attachments in my notes; is it possible that Joplin is just running out of memory? The largest one is over 100 MB. The problem also doesn't seem to be isolated to a single note, it happens no matter which note is selected.
I've tried enabling debug mode but I do not see any errors in the console prior to Joplin crashing (I don't even see the "paused before potential out-of-memory crash" error, I just get a "dev tools is disconnected" once the renderer process crashes). I also do not see anything of interest in the log.txt or the .json file that is generated after the crash.
Is there anywhere else I can look to determine what's causing it to crash?
I believe Joplin is running out of memory, because in Task Manager (I'm on Windows) I see the memory usage climbing steadily in the first few seconds after starting, until it reaches about 4.5 GB and then it crashes.
I discovered that if I disable the OCR feature, Joplin no longer crashes and the memory usage stays low. So in my case it seems to be related to OCR somehow.
