Bug 378741 - Crash on creating new or opening file.
Summary: Crash on creating new or opening file.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.1.3-beta
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
: 379186 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-04-13 14:03 UTC by Bryan McWhirt
Modified: 2017-04-26 08:04 UTC (History)
2 users (show)

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


Attachments
OS X Crash report for Krita 3.1.3-beta1 (100.66 KB, text/plain)
2017-04-13 14:03 UTC, Bryan McWhirt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan McWhirt 2017-04-13 14:03:24 UTC
Created attachment 105010 [details]
OS X Crash report for Krita 3.1.3-beta1

OS: OS X 10.12.4

Unable to open or create a new file. Doing so results in a Segfault.

Attached is the crash report OS X generated to be mailed to Apple.

Brief of report:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]
Comment 1 Halla Rempt 2017-04-13 14:42:32 UTC
Oh! I know what I did wrong. I built master, then re-used the same build dir for 3.1.3-beta, without removing the new-in-master arrange docker. Weirdly enough, the app bundle ran fine on my test system, but it's wrong in any case. I'll fix it for the next build. Thanks for the report!
Comment 2 Bryan McWhirt 2017-04-13 17:35:37 UTC
(In reply to Boudewijn Rempt from comment #1)
> Oh! I know what I did wrong. I built master, then re-used the same build dir
> for 3.1.3-beta, without removing the new-in-master arrange docker. Weirdly
> enough, the app bundle ran fine on my test system, but it's wrong in any
> case. I'll fix it for the next build. Thanks for the report!

Absolutely. If you need an OS X tester I'm happy to oblige. I'm running a MBP 2016 with an Intuous 3 tablet and hoping to get a Cintiq Pro 16 later this year. Once I get a good external hdd I can do builds, but with just the small internal SSD installing XCode and everything takes up too much space.
Comment 3 Halla Rempt 2017-04-13 18:24:28 UTC
> Absolutely. If you need an OS X tester I'm happy to oblige. 

Awesome!

> I'm running a MBP
> 2016 with an Intuous 3 tablet and hoping to get a Cintiq Pro 16 later this
> year. Once I get a good external hdd I can do builds, but with just the small
> internal SSD installing XCode and everything takes up too much space.

Yeah... The 256 gb internal ssd of my mbp 2016 means I can use it _only_ for
building and testing Krita -- there is no space on it to use it for anything
else!
Comment 4 wolthera 2017-04-25 12:04:11 UTC
*** Bug 379186 has been marked as a duplicate of this bug. ***
Comment 5 Hank 2017-04-25 12:26:22 UTC
Sorry for the duplicate. I tried my best to search the bug tracker list with no result.
At least I´m glad I´m not alone.
FWIW: I´m still on macOS Yosemite.

Cheers
Comment 6 Halla Rempt 2017-04-25 14:00:54 UTC
Please try https://download.kde.org/unstable/krita/3.1.3-rc.1/krita-3.1.3-rc.1.dmg, it shouldn't contain the broken plugin.
Comment 7 Hank 2017-04-25 15:50:52 UTC
Thanks Boudewijn Rempt. The rc1 version seems to work so far. Not so sure about the broken plug-in you mentioned. Thanks for the speedy fix though. Much appreciated.

Cheers
Comment 8 Bryan McWhirt 2017-04-25 21:58:57 UTC
Works here so far. I'll give it a run through tomorrow with the tablet at the office to be sure. But for now this issue appears fixed.
Comment 9 Halla Rempt 2017-04-26 08:04:12 UTC
Thasnks for reporting back!