QtWebEngine/ReportingCrashes: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
To clear the cache, manually delete your application settings folders. | To clear the cache, manually delete your application settings folders. | ||
Windows: Delete the directory named after your executable in %APPDATA%, %LOCALAPPDATA% | Windows: Delete the directory named after your executable in %APPDATA%, %LOCALAPPDATA%<br /> | ||
Linux: Delete the directory named after your executable in | Linux: Delete the directory named after your executable in | ||
| Line 18: | Line 19: | ||
TODO: qtdiag, QT_OPENGL=software. | TODO: qtdiag, QT_OPENGL=software. | ||
== Debug Output == | == Getting Debug Output == | ||
Both Qt and Chromium provide valuable debugging output. For Linux, this is usually shown in the console. For Windows though, it will only appear if you launch your app in a debugger, or with a tool like [https://docs.microsoft.com/en-us/sysinternals/downloads/debugview dbgview]. | |||
To increase the debugging log in release mode, run with '--enable-logging --log-level=0'. | |||
Latest revision as of 13:39, 26 March 2019
Random advice on how to debug WebEngine issues. Still WIP.
Deleting application settings
Qt WebEngine does cache things in your local user account, and sometimes this causes crashes or asserts on startup, especially when switching between different Qt (and therefore WebEngine) versions.
To clear the cache, manually delete your application settings folders.
Windows: Delete the directory named after your executable in %APPDATA%, %LOCALAPPDATA%
Linux: Delete the directory named after your executable in
Getting a Stacktrace
To get a better stack trace, launch your application with '--single-process' argument.
Graphics Issues
TODO: qtdiag, QT_OPENGL=software.
Getting Debug Output
Both Qt and Chromium provide valuable debugging output. For Linux, this is usually shown in the console. For Windows though, it will only appear if you launch your app in a debugger, or with a tool like dbgview.
To increase the debugging log in release mode, run with '--enable-logging --log-level=0'.