https://bugs.kde.org/show_bug.cgi?id=387033

Alvin Wong <alvinhoc...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #5 from Alvin Wong <alvinhoc...@gmail.com> ---
OK, Looks like I can reproduce the crash, seem to happen when Input Mode uses
more than one layer. Perhaps due to output having less layers than input.

Also crashes on 4.0 pre-alpha 2 (pretty much expected):

krita.exe caused an Access Violation at location 00007FFC2E9E3DE8 in module
kritaqmic.dll Reading from location FFFFFFFFFFFFFFFF.

AddrPC           Params
00007FFC2E9E3DE8 000000003E9A05B0 0000000026BEA090 0000000026BEA0BC 
kritaqmic.dll!visitNodeWithPaintDevice  [C:/dev/4/64/i/include/QtCore/qdebug.h
@ 146]
00007FFC33A6A8D3 000000003EB1ED40 0000000026BEA090 0000000026BEA0BC 
libkritaimage.dll! ??  
[C:/dev/4/64/krita/libs/image/commands_new/kis_processing_command.cpp @ 35]
00007FFC33AE1EFF 0000000026BEA090 0000000000000000 0000000300000000 
libkritaimage.dll!doStrokeCallback 
[C:/dev/4/64/krita/libs/image/kis_stroke_strategy_undo_command_based.cpp @ 73]
00007FFC33C9C442 000000002679F8D0 00007FFC350B93E0 000000002679F8D0 
libkritaimage.dll!run  [C:/dev/4/64/krita/libs/image/kis_base_node.h @ 320]
00007FFC34D7CF61 000000003EB1ED30 0000000026817E00 0000000000000000 
Qt5Core.dll!QThreadPoolPrivate::clear
00007FFC34D80AA6 0000000000000000 0000000000000000 0000000000000000 
Qt5Core.dll!QThreadStorageData::finish
00007FFC74691FE4 0000000000000000 0000000000000000 0000000000000000 
KERNEL32.DLL!BaseThreadInitThunk
00007FFC76F5EF91 0000000000000000 0000000000000000 0000000000000000 
ntdll.dll!RtlUserThreadStart


Crash location is probably
https://github.com/KDE/krita/blob/d6bfc136a743b2c30e72d8f76edccb3e2b027bc2/plugins/extensions/qmic/kis_import_qmic_processing_visitor.cpp#L73
The obvious mistake is not doing sanity bound checking on `m_images`, but more
probably needs to be done to handle the action properly (perhaps involving
layer deletion).

I don't know enough to comment.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to