Bug report #17113
qgis crash
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Python plugins | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Windows 10 x 64 | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | invalid |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 25012 |
Description
User Feedback¶
running multi distance buffer plugin
Report Details¶
Crash ID: f364d2de70131445cdfae61159017f60b7d638a6
Stack Trace
(Qt5Core) QMetaObject::cast (unknown file):(unknown line) (Qt5Widgets) QGestureRecognizer::unregisterRecognizer (unknown file):(unknown line) (Qt5Widgets) QApplication::notify (unknown file):(unknown line) (qgis_core) QgsApplication::notify qgsapplication.cpp:310 (Qt5Core) QCoreApplication::notifyInternal2 (unknown file):(unknown line) (Qt5Core) QEventDispatcherWin32Private::sendTimerEvent (unknown file):(unknown line) (Qt5Core) QEventDispatcherWin32::processEvents (unknown file):(unknown line) (USER32) CallWindowProcW (unknown file):(unknown line) (USER32) DispatchMessageW (unknown file):(unknown line) (Qt5Core) QEventDispatcherWin32::processEvents (unknown file):(unknown line) (qwindows) qt_plugin_query_metadata (unknown file):(unknown line) (Qt5Core) QEventLoop::exec (unknown file):(unknown line) (Qt5Core) QCoreApplication::exec (unknown file):(unknown line) (qgis_app) main main.cpp:1345 (surveykshak) WinMain mainwin.cpp:122 (surveykshak) __scrt_common_main_seh exe_common.inl:283 (KERNEL32) BaseThreadInitThunk (unknown file):(unknown line) (ntdll) RtlUserThreadStart (unknown file):(unknown line)
QGIS Info
QGIS Version: 2.99.0-Master
QGIS code revision: commit:
Compiled against Qt: 5.7.1
Running against Qt: 5.7.1
Compiled against GDAL: 2.2.1
Running against GDAL: 2.2.1
System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.15063
History
#1
Updated by Giovanni Manghi over 6 years ago
- Resolution set to invalid
- Status changed from Open to Closed
Must be filed in the (3rd party) plugin issue tracker. Thanks.