经常性的闪退并产生了dump文件,大佬们可以帮忙分析解决一下吗,大致看到是QT引起的闪退

STACK_TEXT:
00000002`ee3cb9e0 00007ffe`5560497c : 000001c8`f4f85d70 000001c8`f4f4daa0 00000002`ee3cc040 000001c8`8034d170 : Qt5Core!QCoreApplicationPrivate::sendThroughObjectEventFilters+0x46
00000002`ee3cba40 00007ffe`55603a13 : 000001c8`f4f85d70 00000002`ee3cbb70 00007ffe`555f0000 00000086`0000062f : Qt5Widgets!QApplicationPrivate::notify_helper+0xfc
00000002`ee3cba70 00007ffe`54b32aca : 000001c8`882cc3b0 00007ffe`c5ccf937 00000000`00000000 000001c8`f4f4ab30 : Qt5Widgets!QApplication::notify+0x18b3
00000002`ee3cbfb0 00007ffe`54b7d3c9 : 00000e1a`71c2de1a 00007ffe`c5ccf875 000001c8`882cc3b0 000001c8`f4f4ab30 : Qt5Core!QCoreApplication::notifyInternal2+0xba
00000002`ee3cc020 00007ffe`54b7c63a : 00000000`00000001 00000000`00000000 00000002`ee3cc129 00000000`00000001 : Qt5Core!QEventDispatcherWin32Private::sendTimerEvent+0xf9
00000002`ee3cc070 00007ffe`c5cce7e8 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : Qt5Core!QEventDispatcherWin32::processEvents+0xc4a
00000002`ee3cc190 00007ffe`c5cce229 : 00000000`00003dff 00007ffe`54b7c180 00000000`00020534 000001c8`00000113 : user32!UserCallWinProcCheckWow+0x2f8
00000002`ee3cc320 00007ffe`54b7bf8c : 00007ffe`54b7c180 00000000`00000001 00000002`ee3cc490 000001c8`f4f4ab60 : user32!DispatchMessageWorker+0x249
00000002`ee3cc3a0 00007ffe`87ec2dd9 : 000001c8`f4f9de40 00000000`00000000 000001c8`f4fa7b30 00000000`00000001 : Qt5Core!QEventDispatcherWin32::processEvents+0x59c
00000002`ee3cf4d0 00007ffe`54b2ef2c : 00000000`00000000 00007ffe`00000014 00000000`00000048 00000000`00000003 : qwindows!qt_plugin_query_metadata+0x1f99
00000002`ee3cf500 00007ffe`54b31a94 : 000001c8`f4f5a138 00000000`00000000 00000002`ee3cf6c0 00007ffe`54c51c90 : Qt5Core!QEventLoop::exec+0x1bc
00000002`ee3cf560 00007ff6`2263ecda : 000001c8`f4f85e70 000001c8`f4f59440 00007ff6`227f5ca0 000001c8`f4fa7ac0 : Qt5Core!QCoreApplication::exec+0x154
00000002`ee3cf5c0 00007ff6`22b1ab87 : 00000000`00000000 00000000`00000000 00000000`00000000 000001c8`f4f55cf0 : WindTerm+0x2decda
00000002`ee3cf800 00007ff6`22b11bae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindTerm+0x7bab87
00000002`ee3cf890 00007ffe`c5b57614 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindTerm+0x7b1bae
00000002`ee3cf8d0 00007ffe`c5f026a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000002`ee3cf900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: Qt5Core+46

MODULE_NAME: Qt5Core

IMAGE_NAME: Qt5Core.dll

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_Qt5Core.dll!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 5.15.2.0

FAILURE_ID_HASH: {e187daa5-db35-d98d-1840-c9f4590b5968}

Followup: MachineOwner

Start by examining the supplied Windows dump and stack frames around Qt5Core.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters and the WindTerm frames. Confirm whether the INVALID_POINTER_READ crash is reproducible on Windows 10 x64 with Qt 5.15.2; done means identifying the cause and verifying that the recurring crash no longer occurs.

Written by the indexing model from the issue text.