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

[jpnurmi]

I gave it a quick try, but couldn't reproduce with Qt 6 and MSVC 2022 that I happened to have installed.

Does something like this reproduce it for you? Which backend are you using?

#include <QtCore>
#include <sentry.h>

class Victim : public QObject
{
public:
    explicit Victim(QObject *parent = nullptr) : QObject(parent), m_child(new QObject(this))
    {
        m_child->setObjectName("child");
    }

    void scheduleCrash()
    {
        QTimer::singleShot(100, [this] { crash(); });
    }

private:
    void crash() const
    {
        m_child->objectName();
    }

    QObject *m_child = nullptr;
};

int main(int argc, char *argv[])
{
    sentry_options_t *options = sentry_options_new();
    sentry_options_set_dsn(options, SENTRY_DSN);
    sentry_options_set_debug(options, 1);
    sentry_init(options);

    QCoreApplication app(argc, argv);

    Victim *victim = new Victim;
    victim->scheduleCrash();
    delete victim;

    return app.exec();
}