Can't open file - Designer crashes everytime

[jus142]

Hey there,

I want to finish a project of someone else. He send me the file (.afpub) but everytime I try to open the document the program crashes. 

I can open affinity designer regulary and start a new project. But everytime I try to load the existing file the programm closes itself without any message.

I have installed the new update for affinity designer today before starting work. All windows updates are installed.  

It is a file of 24 MB, I am using Windows10, the file was created on an mac pc. Can that be the problem? Anything I can do?

Thanks for your help! 
 

[v_kyr]

Hi and welcome!

If you are able to reach the Preferences settings before crashing, switch there to the Performance settings and disable the hardware acceleration settings. Afterwards restart and retry. 

• If you can't reach the performance preferences settings, since the app crashes before, then alter and disable the hardware acceleration setting manually from outside and start and tryout the app afterwards. - Alternatively you can also use and tryout this tool to disable the settings.

Or you can try out one of the latest Beta builds which should have addressed many issues related to these OpenCL issues!

If all above mentioned doesn't help, look for possible Affinity crash reports, which should then hopefully tell the cause of all evil ...

• [FAQ] Where to find Crash Reports 

[jus142]

Thank you for your advice.
Unfortunaly nothing worked out. 
I am not able to acitvate the hardware accelariton settongs (because of the windows version). 
With the Beta Version I have the same problem - the programm crashes as well. 

And the Crash Reports are empty. I can open them with bluescreenview, but it shows no content. 

So do you think it is a problem of the filesize? Maybe I can ask the orginator to send it in parts to avoid this problem... 
I don't have a clue what else I can do...
 

[v_kyr]

24 minutes ago, jus142 said:

I am not able to acitvate the hardware accelariton settongs (because of the windows version). 

Not sure what you mean with "cause of the Windows version" here? Aren't you able to reach there, to the Designer preferences settings, in order to disable possible default enabled hardware acceleration settings?

24 minutes ago, jus142 said:

And the Crash Reports are empty. I can open them with bluescreenview, but it shows no content.

Does this mean there aren't any crash dump files at all, or that you just can't view their contents? Take a look via Explorer etc. if there are any actual files and their file size isn't 0. - Since these then would give hints for analyzes what might lead to crashings. - Or possible Windows system crash report logs would help too here.

24 minutes ago, jus142 said:

So do you think it is a problem of the filesize?

Hard to tell since we don't know certain specs of your Win system, like available RAM, available amount of free disk space ... etc. But a 24 MB file usually shouldn't be a problem here.

We have to limit/encircle the possible cause of crashing here, which can have various different causes, like for example OpenCL and thus GPU driver based hardware acceleration, or possible crashing due to font loading problems, or some Windows .Net runtime library version problem ... etc. etc.

[jus142]

31 minutes ago, v_kyr said:

Not sure what you mean with "cause of the Windows version" here? Aren't you able to reach there, to the Designer preferences settings, in order to disable possible default enabled hardware acceleration settings?

Does this mean there aren't any crash dump files at all, or that you just can't view their contents? Take a look via Explorer etc. if there are any actual files and their file size isn't 0. - Since these then would give hints for analyzes what might lead to crashings. - Or possible Windows system crash report logs would help too here.

Hard to tell since we don't know certain specs of your Win system, like available RAM, available amount of free disk space ... etc. But a 24 MB file usually shouldn't be a problem here.

We have to limit/encircle the possible cause of crashing here, which can have various different causes, like for example OpenCL and thus GPU driver based hardware acceleration, or possible crashing due to font loading problems, or some Windows .Net runtime library version problem ... etc. etc.

1) It says I have to use Windows10 (version 10.0.19042) to chance the hardware acceleration settings. But I just use Windows 8.1.
 

2) I have crash reports (1.300 to 2.200 KB,) but I can't view their contents. I downloadet bluescreenview for that. It opens the file but it shows no information, no matter which of the 11 crash reports I try. 

Would you recomend anonther program for reading them? 

 

 

I'm sorry for my bad english but I am very thankful for your advice! 
It seems as if there can be really a lot of possible reasons for that problem.... 

 

[v_kyr]

14 minutes ago, jus142 said:

2) I have crash reports (1.300 to 2.200 KB,) but I can't view their contents. I downloadet bluescreenview for that. It opens the file but it shows no information, no matter which of the 11 crash reports I try. 

Would you recomend anonther program for reading them? 

Well I'm not sure their contents would make any sense for you, since they contain program runtime call execution hierarchy backtraces etc. So something developers are more familiar with to read and analyze. - Thus you may want to attach (upload) them here in this thread, or under some posting you have to make in the "Designer Bugs found on Windows" forum section.

Wenn Du kannst und die Dateien nicht zu gross sind, dann füge die Crash Dump Dateien einfach diesem Thread hier bei (lade sie mit hoch). Ansonsten alternativ kannst Du auch ein entsprechendes Posting im "Designer Bugs found on Windows" Forumsbereich erstellen und diese dort beifügen!

[jus142]

Here's one of the crash reports:

0dd9a3ea-f2bc-4724-bd91-c9bbe7392fff.dmp

[v_kyr]

30 minutes ago, jus142 said:

Here's one of the crash reports:

0dd9a3ea-f2bc-4724-bd91-c9bbe7392fff.dmp 1.34 MB · 1 download

Here's a corresponding stackwalk output of that dump file ....

• output.txt

Quote

Operating system: Windows NT
                  6.3.9600 19843
CPU: amd64
     family 6 model 58 stepping 9
     4 CPUs

GPU: UNKNOWN

Crash reason:  0xe0434352 / 0x00000001
Crash address: 0x7ffdf6eb7afc
Process uptime: 19 seconds

Thread 0 (crashed)
 0  KERNELBASE.dll + 0x7afc
    rax = 0x00007ffded1ba5e5   rdx = 0x0000000000000001
    rcx = 0x000000493c8adae8   rbx = 0x00000000e0434352
    rsi = 0x0000000000000001   rdi = 0x0000000000000005
    rbp = 0x000000493c8ae3d0   rsp = 0x000000493c8ade50
     r8 = 0x00007ffd00000000    r9 = 0x00007ffdca9e31f0
    r10 = 0x0000000000000001   r11 = 0x000096017a0aa426
    r12 = 0x0000000000004000   r13 = 0x00000049413a01c8
    r14 = 0x000000493c8adfe8   r15 = 0x00000049413a0198
    rip = 0x00007ffdf6eb7afc
    Found by: given as instruction pointer in context
 1  Serif.Interop.Persona.ni.dll + 0x27e4d9c
    rbp = 0x000000493c8ae470   rsp = 0x000000493c8ae3e0
    rip = 0x00007ffdba584d9c
    Found by: previous frame's frame pointer
 2  Serif.Interop.Persona.ni.dll + 0x2835cb4
    rbp = 0x000000493c8ae4e0   rsp = 0x000000493c8ae480
    rip = 0x00007ffdba5d5cb4
    Found by: previous frame's frame pointer
 3  Serif.Interop.Persona.ni.dll + 0x27c689f
    rbp = 0x000000493c8ae670   rsp = 0x000000493c8ae4f0
    rip = 0x00007ffdba56689f
    Found by: previous frame's frame pointer
 4  Serif.Interop.Persona.ni.dll + 0x27dd63d
    rbp = 0x000000493c8ae730   rsp = 0x000000493c8ae680
    rip = 0x00007ffdba57d63d
    Found by: previous frame's frame pointer
 5  Serif.Interop.Persona.ni.dll + 0x27d89d0
    rbp = 0x000000493c8ae790   rsp = 0x000000493c8ae740
    rip = 0x00007ffdba5789d0
    Found by: previous frame's frame pointer
...
...

Post your dump and the output together into a Win 8.1 related bug report under the "Designer Bugs found on Windows" forum section, so the devs will recognize it and can look for why it crashes in KERNELBASE.dll due to Serif.Interop.Persona.ni.dll here!

[jus142]

24 minutes ago, v_kyr said:

Here's a corresponding stackwalk output of that dump file ....

• output.txt 106.55 kB · 0 downloads

Post your dump and the output together into a Win 8.1 related bug report under the "Designer Bugs found on Windows" forum section, so the devs will recognize it and can look for why it crashes in KERNELBASE.dll due to Serif.Interop.Persona.ni.dll here!

Thank you very much for your help! 
I posted it in the recommended forum section and hope someone there could help me. 

Thanks a lot! 

[v_kyr]

As you can see, they already solved your file problem, which is due to parsing usually unallowed OS related file pathname definitions here. So in this case something which isn't handled file wise in a well behaving cross-platform manner. - They will have to fix that by also include some pretesting/proving first, if any referenced image path confirms to cross-platform filepath character rules or not, so that generated Affinity files still can keep their portability between their OS related versions.