Crash dump: Renderer process gone

Operating system

Linux

Joplin version

3.0.13

Desktop version info

Joplin 3.0.13 (prod, linux)

Client ID: f5ca84ca8e4c4cd3b75f35848b431a1f
Sync Version: 3
Profile Version: 47
Keychain Supported: No

Revision: 599cf5b

Backup: 1.4.1

Sync target

Joplin Server

Editor

Markdown Editor

What issue do you have?

I have observed a joplin_crash_dump_*.json file created in my Home directory when I reboot my computer. I have uploaded this file for your reference. I have never observed this behaviour before and it's something new I'm seeing only after upgrading to Joplin v3.*

Log file

joplin_crash_dump_20240718T123519.json.txt (111 KB)

In a relatively recent release (v2.14.11) Joplin was changed to automatically create a crash_dump file if the app crashed. Since then I, like you, have been regularly getting these created. I am not having any problems with Joplin and I believe that if Joplin is still running when you shut down your machine it treats it as a crash and so the file is created. I do not use Windows or Mac so I cannot see if the same happens there or if it is just that the AppImage is not capable of understanding that the system is shutting down rather than the app crashing.

Thanks a lot for your response. Good to know I'm not the only one experiencing this. Will just ignore these crash dump files then, as you suggest. Cheers!

It's only what I have observed that makes me think it is the shutdown process causing this. Sometimes however a dump file is not created so I guess that Joplin has to be in a particular state when the shutdown occurs to cause the dump file to be generated. Whether Joplin on Linux should be able to gracefully quit when a system shutdown is broadcast is another matter. I intended to experiment with this further to see if it was worth submitting an issue, I just haven't had the time yet.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.