Priority: Not Evaluated
Resolution: Won't Do
Affects Version/s: 5.7.0
Fix Version/s: None
Environment:Windows 10. Qt 5.7.0 (haven't tested on 5.7.1 yet)
(We use _CrtDbgReportW (via _ASSERT) to help us pop up a window during asserting. However, we've recently started working with QtWebEngine, and noticed that as soon as you work with a QtWebEnginePage, it seems to disable _CrtDbgReportW.
Steps to reproduce: See the attached example - updated for simpler _ASSERT-only.
Expected Results: 3 assert windows popup
Actual Result: Only the 1st window pops up
Is there something I'm doing wrong?
Looking into the chromium project, it seems process_startup_helper.cc::SetupCRT is disabling CRT_ASSERT unless the commandline argument "--disable-breakpad" is set (note: this logic seems backwards?). I can't seem to find any documentation on this commandline argument, and the codebase indicates its only used here.
We're aware of the workaround to get the current ReportMode before initializing the QWebEnginePage, and then setting it back afterwards, but this seems unusual. Any alternatives or guidelines for better practise would be a big help, but this seems like a bug to me.