An uncaught crash

[theoelton203]

Description
In a Qt5 application built with VS2019 on Windows 10, a crash occurs when an asynchronously executed lambda captures this . The original object is destroyed before the lambda runs, leaving a dangling this pointer. When the lambda later accesses a member variable or calls a member function, an access violation triggers a hard crash. However, Sentry does not capture this crash – no report is generated, and the crash remains invisible in the Sentry dashboard.

Environment

• OS: Windows 10, 64-bit
• Compiler: MSVC 19 (Visual Studio 2019)
• Sentry SDK version: 0.13.8
• Qt version: 5.15.2

Let me know if you need any adjustments.

[linear-code]

NATIVE-184