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

            Bug ID: 336914
           Summary: Blur filter crashes if vertical component is adjusted
                    independent of horizontal. Y>X
    Classification: Unclassified
           Product: krita
           Version: git master
          Platform: unspecified
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Filters
          Assignee: krita-bugs-null@kde.org
          Reporter: stuartmd@kogmbh.com

Repeatable crash.

1. Create an image (8-bit RGB)
2. Select Blur Filter
3. Unlock horz/vertical components
4. Adjust vertical component
(crash)

The stack trace is:
>	kritaimage.dll!KisConvolutionWorkerSpatial<RepeatIteratorFactory>::loadPi=
xelToCache(double * * cache, const unsigned char * data, int index) Line 53=
	C++
=20=20=20=20
kritaimage.dll!KisConvolutionWorkerSpatial<RepeatIteratorFactory>::moveKern=
elRight(KisSharedPtr<KisRepeatVLineIteratorPixelBase<KisVLineIterator2>
> & kitSrc, double * * pixelPtrCache) Line 327    C++
=20=20=20=20
kritaimage.dll!KisConvolutionWorkerSpatial<RepeatIteratorFactory>::execute(=
const
KisSharedPtr<KisConvolutionKernel> kernel, const KisSharedPtr<KisPaintDevic=
e>
src, QPoint srcPos, QPoint dstPos, QSize areaSize, const QRect & dataRect) =
Line
176    C++
     kritaimage.dll!KisConvolutionPainter::applyMatrix(const
KisSharedPtr<KisConvolutionKernel> kernel, const KisSharedPtr<KisPaintDevic=
e>
src, QPoint srcPos, QPoint dstPos, QSize areaSize, KisConvolutionBorderOp
borderOp) Line 150    C++
=20=20=20=20
kritablurfilter.dll!KisBlurFilter::processImpl(KisSharedPtr<KisPaintDevice>
device, const QRect & rect, const KisFilterConfiguration * config, KoUpdate=
r *
progressUpdater) Line 108    C++
     kritaui.dll!KisFilterStrokeStrategy::doStrokeCallback(KisStrokeJobData=
 *
data) Line 106    C++
     kritaimage.dll!KisUpdateJobItem::run() Line 62    C++


This seems to occur for the condition y>x;
If the program crashes with preview enabled and y>x then the blur filter
crashes prior to the display of the dialog.

for y<x then the filter time takes an usually long time even for a small
1024x1024 single layer file. During this time, the user can see the layer
change progress bar applying numerous times with a main level of progress w=
hich
slowly increments but then seems to update from a slightly lower progress.

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