Jump to content

Recommended Posts

Posted

Dear all,

my daugther has worked on this file for the better part of our vacation when suddenly, Affinity Designer for Mac closed and would not open the file again. The App opens ok and she can open other files, but not this one. Oddly, the file can be opened and worked with on a Win10 System (which our other daughter uses).

I have tried the usual, completely remove Designer (incl files in Library/Application support), restarting MacOS, reinstalling, but to no avail. I am attaching the crash-report.

Does anyone have an idea of how to avoid this problem. It is not this particular file that is important; my daughter works on various projects for school and other purposes and fears that it will happen again.

Any hint will be appreciated.

Ingo

meer ausprobieren neu.afdesign affinity_report

Posted

Well the crash report ...

Quote

Crashed Thread:        5  Dispatch queue: com.apple.root.utility-qos

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x0000700007fe1fc8
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [940]

VM Regions Near 0x700007fe1fc8:
    Stack                  0000700007f5f000-0000700007fe1000 [  520K] rw-/rwx SM=COW  thread 4
--> STACK GUARD            0000700007fe1000-0000700007fe2000 [    4K] ---/rwx SM=NUL  stack guard for thread 5
    Stack                  0000700007fe2000-0000700008064000 [  520K] rw-/rwx SM=COW  thread 5

...
Thread 5 Crashed:: Dispatch queue: com.apple.root.utility-qos
0   liblibpersona.dylib               0x00000001272d823d Node::GetBaseToSpreadTransform(Kernel::NonCounted<Node const>) const + 45
1   liblibpersona.dylib               0x00000001272d8240 Node::GetBaseToSpreadTransform(Kernel::NonCounted<Node const>) const + 48
2   liblibpersona.dylib               0x00000001272d8240 Node::GetBaseToSpreadTransform(Kernel::NonCounted<Node const>) const + 48
3   liblibpersona.dylib               0x00000001272d8240 Node::GetBaseToSpreadTransform(Kernel::NonCounted<Node const>) const + 48
...

... tells that a KERN_PROTECTION_FAILURE occured ...

Quote

KERN_PROTECTION_FAILURE: The crashed thread tried to use a valid memory address that’s protected. Some types of protected memory include read-only memory regions, or nonexecutable memory regions. See Use VM Region Info to Locate the Memory in Your App’s Address Space for how to distinguish the type of protected memory.

The dereferenced memory address (in your case) is 0x0000700007fe1fc8, with the region containing this memory address identified by the arrow. The address is located in a special memory region called the stack guard, which is a memory region that buffers the stack of a thread from the stack of another thread. The PRT column shows the current permission attributes for the memory regions, with r indicating the memory is readable, w indicating the memory is writable, and x indicating the memory is executable.

Because the stack guard region has no permissions, all memory accesses to this region are invalid, and the crash report is identifying this memory access as a violation of the memory protection attributes.

rw-/rwx Read, write and execution permissions for the region (in your case ---/rwx). The first set of flags specifies the current protection for the region. The second set of values specifies the maximum protection for the region. If an entry contains a dash (-), the process does not have the target permission!

The protection mode describes the access restrictions for the memory region. A memory region contains separate flags for read, write, and execution permissions. Each virtual memory region has a current permission, and a maximum permission. In the output from vmmap, the current permission appears first followed by the maximum permission. Thus, if the permissions are “r--/rwx“ the page is currently read-only but allows read, write, and execution access as its maximum allowed permissions. Typically, the current permissions do not permit writing to a region. However, these permissions may change under certain circumstances. For example, a debugger may request write access to a page in order to set a breakpoint.

... at least on MacOS.

If that file ...

img-preview.jpg.b49652389ec594050d32ae50d6c1a686.jpg

can be opened on a Win 10 box with AD instead, then I would try to save it from there under a different file name (use "Save As..." there) and exchange that file to test it then again under MacOS, in order to see if the behavior might now be possibly different.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted

Like the OP, I found their attached file crashes the current retail version of Designer.
But out of curiosity I tried the problem file in the current Designer beta and it opens just fine, no problems.

macOS 12.7.6  15" Macbook Pro, 2017  |  4 Core i7 3.1GHz CPU  |  Radeon Pro 555 2GB GPU + Integrated Intel HD Graphics 630 1.536GB  |  16GB RAM  |  Wacom Intuos4 M

Posted
3 hours ago, v_kyr said:

If that file can be opened on a Win 10 box with AD instead, then I would try to save it from there under a different file name (use "Save As..." there) and exchange that file to test it then again under MacOS, in order to see if the behavior might now be possibly different.

You can try this one.

meer ausprobieren neu_win10.afdesign

AP, AD & APub user, running Win10

Posted

Looks to be more a MacOS AD v1.9.3 related bug here!

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted
9 hours ago, markw said:

Like the OP, I found their attached file crashes the current retail version of Designer.
But out of curiosity I tried the problem file in the current Designer beta and it opens just fine, no problems.

Same here. 

All 3 1.10.8, & all 3 V2.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Posted

Hi @Ingo_Germany,

Welcome to the Affinity Forums :)

I can confirm that I've been able to replicate the crashing on macOS here, but as other forum members have noticed - the same crash does not occur in the Windows version or the beta version for all platforms (mac, Windows & iPad).

For this reason, we are marking this issue as 'fixed' for the beta versions. I hope this helps!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.