Note: Advice in this article will only work for JxBrowser 6. See the corresponding article for JxBrowser 7 here.(注意：本文中的建议仅适用于JxBrowser6，JxBrowser7相应文章请点击这里。)
JxBrowser runs all native code and Chromium engine in separate processes. When unexpected error happens in Chromium engine you might see unexpected process termination. To find out root cause of the error we need that you collect error info from generated crash dump files.(JxBrowser在单独的进程中运行所有本机代码和Chromium引擎。当Chromium引擎发生意外错误时，您可能会看到意外的过程终止。为了找出错误的根本原因，我们需要您从生成的故障转储文件中收集错误信息。)
When error happens in Chromium engine, the crash dump file with all necessary information about the error is automatically generated on Mac OS X. You can find generated crash dump files in Console app, User Diagnostic Reports log list. JxBrowser report has the jxbrowser_2015-04-05-150659_Vladimirs-MacBook-Pro.crash name.(如果Chromium引擎中发生错误，则会在Mac OS X上自动生成包含有关该错误的所有必要信息的崩溃转储文件。您可以在Console应用程序的“用户诊断报告”日志列表中找到生成的崩溃转储文件。 JxBrowser报告具有jxbrowser_2015-04-05-150659_Vladimirs-MacBook-Pro.crash名称。)
Copy content of this crash report and send it to us as attachment to your support ticket or share the generated core dump file with the JxBrowser Support team using an online file sharing service such as Dropbox, Google Drive, etc.(复制此崩溃报告的内容，并将其作为支持票的附件发送给我们，或使用在线文件共享服务（例如Dropbox，Google云端硬盘等）与JxBrowser支持团队共享生成的核心转储文件。)
Here's how crash report in Console app looks:(图略)