By default, on Linux platforms nothing happens when the Chromium engine, used by JxBrowser, has been unexpectedly crashed. To collect information about the native crash and determine root cause of the issue, we need to get a core dump file. The core dump file is generated by operating system. By default, core dump file generation is disabled. To enable code dump file generation you need to configure your Linux environment using specific steps.


The following short instruction explains how to enable core dump generation on Ubuntu:


This instruction is valid for JxBrowser 6.16 and higher. With the previous JxBrowser versions, core dump file generation isn't supported.


Configuring Ubuntu 14.04 and higher

By default, Ubuntu doesn't generate crash dump files. To enable core dump file generation you must modify the /proc/sys/kernel/core_pattern file via the following command:

$ echo '/tmp/core.%e.%p.%t' > /proc/sys/kernel/core_pattern

It will change a path for the core dump files, so those files would have the name with the /tmp/core.exe_name.pid.time pattern.

Also, you must change the quota for storing dump files with the next command:

$ ulimit -c unlimited

After reboot all the changes will be reverted to default. To prevent this you need to edit the /etc/sysctl.conf file and set the kernel.core_pattern parameter to the required value. For example, in the /etc/sysctl.conf file put/modify the following property:

kernel.core_pattern = /tmp/core.%e.%p.%t

To enable core dump files generation on the operating system startup you must add the following line to /etc/profile:

ulimit -c unlimited

When crash happens in the Chromium engine, the core dump file will be generated and saved in the /tmp directory with the core.%e.%p.%t name.


Please share the generated core dump file with the JxBrowser Support team using an online file sharing service such as Dropbox, Google Drive, etc.