Bug 422982 - Segfault in KisNodeProgressProxy::setRange
Summary: Segfault in KisNodeProgressProxy::setRange
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 4.2.8
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-14 17:32 UTC by Jeremy Rose
Modified: 2020-06-14 18:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Full crash report (98.70 KB, text/plain)
2020-06-14 17:32 UTC, Jeremy Rose
Details
attachment-9265-0.html (1.51 KB, text/html)
2020-06-14 18:03 UTC, Jeremy Rose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Rose 2020-06-14 17:32:41 UTC
Created attachment 129359 [details]
Full crash report

SUMMARY
Program crashed while painting.

STEPS TO REPRODUCE
I can't reproduce this, but in case one of these seems relevant: I was messing with filter layers on a clone layer, outline selection and clearing (w/ Delete), while undoing.


SOFTWARE/OS VERSIONS
macOS: 10.14.6

ADDITIONAL INFORMATION

Here's the stack trace (the full crash report is attached):

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libkritaimage.18.dylib        	0x000000010ff43a3a KisNodeProgressProxy::setRange(int, int) + 42
1   libkritawidgetutils.18.dylib  	0x00000001109310e8 KoProgressUpdater::updateUi() + 712
2   org.qt-project.QtCore         	0x000000011213ef55 QMetaObject::activate(QObject*, int, int, void**) + 1765
3   org.qt-project.QtCore         	0x0000000112146bf2 QTimer::timerEvent(QTimerEvent*) + 98
4   org.qt-project.QtCore         	0x0000000112137e78 QObject::event(QEvent*) + 104
5   org.qt-project.QtWidgets      	0x0000000110f2c110 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
6   org.qt-project.QtWidgets      	0x0000000110f2d4c5 QApplication::notify(QObject*, QEvent*) + 581
7   libkritaui.18.dylib           	0x000000010ecc9ada KisApplication::notify(QObject*, QEvent*) + 26
8   org.qt-project.QtCore         	0x000000011210f384 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
9   org.qt-project.QtCore         	0x0000000112166bf2 QTimerInfoList::activateTimers() + 930
10  libqcocoa.dylib               	0x000000011496b062 0x114937000 + 213090
11  com.apple.CoreFoundation      	0x00007fff4253bd17 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12  com.apple.CoreFoundation      	0x00007fff4253bcbd __CFRunLoopDoSource0 + 108
13  com.apple.CoreFoundation      	0x00007fff4251f6d3 __CFRunLoopDoSources0 + 283
14  com.apple.CoreFoundation      	0x00007fff4251ec45 __CFRunLoopRun + 1189
15  com.apple.CoreFoundation      	0x00007fff4251e54e CFRunLoopRunSpecific + 455
16  com.apple.HIToolbox           	0x00007fff4177d1ab RunCurrentEventLoopInMode + 292
17  com.apple.HIToolbox           	0x00007fff4177cded ReceiveNextEventCommon + 355
18  com.apple.HIToolbox           	0x00007fff4177cc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
19  com.apple.AppKit              	0x00007fff3fb1477d _DPSNextEvent + 1135
20  com.apple.AppKit              	0x00007fff3fb1346b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
21  com.apple.AppKit              	0x00007fff3fb0d588 -[NSApplication run] + 699
22  libqcocoa.dylib               	0x000000011496be68 0x114937000 + 216680
23  org.qt-project.QtCore         	0x000000011210aacf QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 431
24  org.qt-project.QtCore         	0x000000011210f9d2 QCoreApplication::exec() + 130
25  org.krita                     	0x000000010d9924e6 main + 10806
26  libdyld.dylib                 	0x00007fff6e4873d5 start + 1
Comment 1 Halla Rempt 2020-06-14 17:33:42 UTC
Ah, this was fixed for 4.3.0 -- second beta now available, final release this week.
Comment 2 Jeremy Rose 2020-06-14 18:03:29 UTC
Created attachment 129361 [details]
attachment-9265-0.html

Fantastic, thanks! Sorry for the noise, I searched for the top of the stack
trace and didn't find anything. Glad to hear it's fixed :)


On Sun, Jun 14, 2020 at 10:33 AM Boudewijn Rempt <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=422982
>
> Boudewijn Rempt <boud@valdyas.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |boud@valdyas.org
>              Status|REPORTED                    |RESOLVED
>          Resolution|---                         |FIXED
>
> --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
> Ah, this was fixed for 4.3.0 -- second beta now available, final release
> this
> week.
>
> --
> You are receiving this mail because:
> You reported the bug.