Publisher 1.10.5 crashes when I select an inserted image and attempt any action on it.

[lesbillbell]

Publisher 1.10.4 on Windows 10 and 11 crashes when I select an inserted image and attempt any action on it such as moving it or clicking on the 'float with text' icon.

Is there a crash report somewhere in the system? Where would it be located? 

Would it help to change the persona to Photo?

Will this bug be fixed very soon?

[walt.farrell]

2 hours ago, lesbillbell said:

Is there a crash report somewhere in the system? Where would it be located

 

[lesbillbell]

Thank you Walt Farrell. I have many crash reports. How can I get to speak to a member of the support team?

[walt.farrell]

They should be here eventually. It's a small team, supporting a lot of users, and sometimes it takes longer than we (or they) would like. Also, your initial post was after business hours for them, and it's now the weekend, which may delay response.

In the meantime, you might try making sure your GPU drivers are up-to-date, and checking the list of third-party applications that cause problems. And if you feel like uploading one of the recent crash reports, one of the forum users may be able to provide some hints.

You might also try disabling Hardware Acceleration in your Publisher Preferences (Edit > Preferences, then click on Performance)

What kind of graphics card do you have, and what driver version?

[lesbillbell]

Thanks again, it's good of you to respond.

I don't use any of those third-party applications. I don't think I I have a separate GPU. The Display Adapter is an Intel (R) UHD Graphics 620, driver version 27.20.100.9664 (01/06/2021).

I disabled hardware acceleration in Publisher Preferences and restarted Publisher, but when I selected an image and clicked on 'inline with text' icon the the program immediately closed, again.

I've uploaded the most recent crash report file.

 

2f0a84c7-b2a8-4691-ae83-129a8619cc52.dmp

[lesbillbell]

Even worse. I avoided the issue described by deleting and replacing images, setting them inline with text and setting text wrap settings to 'jump', and saving the file (with history), then I inadvisedly clicked on an image that had not been replaced and, clicking the inline with text icon, the program crashed again - when I reopened the previously saved file, images that had been saved in the right place were scattered higgledy-piggledy.

9cb4738f-5194-4d05-99d3-2966c4d0015e.dmp

[Callum]

Hi Lesbillbell,

I apologise for the delayed response. When the app crashes is it typically when you are applying text wrap settings to your image or trying to pin the image? If you create a brand new document and place one of your images in it can you replicate the crash? The crash report seems to point to this being a problem with a pinned object. Is the image or the frame its being placed into pinned at all?

Thanks
C

[v_kyr]

The crash reports point to libStory.dll ...

Quote

Operating system: Windows NT
                  10.0.22000 434
CPU: amd64
     family 6 model 142 stepping 11
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x28
Process uptime: 404 seconds

Thread 0 (crashed)
 0  libStory.dll + 0x2233bb
    rax = 0x00000041241fdb10   rdx = 0x0000000000000001
    rcx = 0x0000000000000000   rbx = 0x00000041241fdb10
    rsi = 0x0000000000000000   rdi = 0x00000182f212a8d0
    rbp = 0x00000041241fdb60   rsp = 0x00000041241fda30
     r8 = 0x0000000000000000    r9 = 0x0000000000000001
    r10 = 0x0000017ab42d0000   r11 = 0x00000041241fda40
    r12 = 0x00000182f13320c0   r13 = 0x0000000000000000
    r14 = 0x00000182fa1e1268   r15 = 0x00000182f1c5a5d0
    rip = 0x00007ffdf1af33bb
    Found by: given as instruction pointer in context
 1  libpersona.dll + 0x20d1215
    rbp = 0x00000041241fdb60   rsp = 0x00000041241fda60
    rip = 0x00007ffd96ba1215
    Found by: stack scanning
 2  libpersona.dll + 0xe9a7585
    rbp = 0x00000041241fdb60   rsp = 0x00000041241fda90
    rip = 0x00007ffda3477585
    Found by: stack scanning

Quote

Operating system: Windows NT
                  10.0.22000 434
CPU: amd64
     family 6 model 142 stepping 11
     8 CPUs

GPU: UNKNOWN

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x28
Process uptime: 2001 seconds

Thread 36 (crashed)
 0  libStory.dll + 0x2233bb
    rax = 0x000000480743ee60   rdx = 0x0000000000000001
    rcx = 0x0000000000000000   rbx = 0x000000480743ee60
    rsi = 0x0000000000000000   rdi = 0x000001b64f22e3d0
    rbp = 0x000000480743eed0   rsp = 0x000000480743eda0
     r8 = 0x0000000000000000    r9 = 0x0000000000000000
    r10 = 0xffffffffffff9508   r11 = 0x000000480743edb0
    r12 = 0x000001b65002c400   r13 = 0x000000480743f010
    r14 = 0x000001b679430940   r15 = 0x000001b65dea3780
    rip = 0x00007ff9410833bb
    Found by: given as instruction pointer in context
 1  libpersona.dll + 0x20cae48
    rbp = 0x000000480743eed0   rsp = 0x000000480743edd0
    rip = 0x00007ff8f01aae48
    Found by: stack scanning
 2  ntdll.dll + 0x27631
    rbp = 0x000000480743eed0   rsp = 0x000000480743ee00
    rip = 0x00007ff9ab5c7631
    Found by: stack scanning
 3  ntdll.dll + 0x27631
    rbp = 0x000000480743eed0   rsp = 0x000000480743ee30
    rip = 0x00007ff9ab5c7631
    Found by: stack scanning
 4  ucrtbase.dll + 0x1218b
    rbp = 0x000000480743eed0   rsp = 0x000000480743eea0
    rip = 0x00007ff9a933218b
    Found by: stack scanning
 5  libpersona.dll + 0xd9713b5
    rbp = 0x000000480743eed0   rsp = 0x000000480743eed0
    rip = 0x00007ff8fba513b5
    Found by: stack scanning
 6  libpersona.dll + 0x20ccba2
    rsp = 0x000000480743ef00   rip = 0x00007ff8f01acba2
    Found by: stack scanning
 7  Serif.Interop.Persona.ni.dll + 0x27abb0f
    rsp = 0x000000480743ef40   rip = 0x00007ff91b86bb0f
    Found by: stack scanning
 8  clr.dll + 0x24fe
    rsp = 0x000000480743efa0   rip = 0x00007ff988d924fe
    Found by: stack scanning
 9  libpersona.dll + 0x20cb378
    rsp = 0x000000480743efe0   rip = 0x00007ff8f01ab378
    Found by: stack scanning
10  libpersona.dll + 0x20cbccf
    rsp = 0x000000480743f010   rip = 0x00007ff8f01abccf
    Found by: stack scanning
11  libpersona.dll + 0x2972a84
    rsp = 0x000000480743f070   rip = 0x00007ff8f0a52a84
    Found by: stack scanning

 

[lesbillbell]

Hi @Callum thanks for your response. I understand how busy you must get. I easily reproduced the issue with half a page of text and one image. I inserted the image using File -> place, then clicked on 'inline with text' and also made the text wrap settings 'jump'. I clicked on the Move tool icon and moved the image a bit. I saved the document with history and opened it again. Then I tried to move the image again, and the program terminated.

I don't understand 'pinning' an image, so I probably didn't. I didn't use a frame for the image.

Crash report attached.

e38b3c5c-cc71-4872-8e7a-e74a02a014aa.dmp

[lesbillbell]

Hi @v_kyr

Thanks to you too for that reading of the crash report. I wonder if the dll is corrupted? But it is unlikely on two different computers.

Les

[lesbillbell]

Hi @Callum any news on this issue please?

[lesbillbell]

Please @walt.farrell  @Callum   why has there been no response on this disabling bug since 9 February? I was asked to replicate the problem and easily did, uploading a crash report. There has been a resounding silence. 

[Callum]

On 2/14/2022 at 10:02 AM, lesbillbell said:

Hi @Callum any news on this issue please?

My apologies I had to take time off last week and unfortunately some of my threads were not picked up by anyone else in the meantime. I have just been looking into this with a member of our QA team. The QA team confirmed my previous speculation that the log does indeed point towards a pinned object. Is the image in question pinned or inline with a story at all? If possible could you provide a copy of the document so I can try and replicate this here?

Thanks
C

[lesbillbell]

Thanks @Callum apology accepted. I am uploading the crude test file with which I replicated the crash behaviour.

imagecrashtest.afpub

[Callum]

2 hours ago, lesbillbell said:

Thanks @Callum apology accepted. I am uploading the crude test file with which I replicated the crash behaviour.

imagecrashtest.afpub 1.35 MB · 0 downloads

Thank you for providing the file so quickly, I can recreate this here at my end I'm just waiting for a member of our QA team to have a look into the cause of the issue. I noticed via the Resource Manager that this file was placed from your One Drive is this method always used when placing this image? Does this only happen with this one image or is it any that you import?

[lesbillbell]

Hi @Callum, thank you for your attention to this issue. My first crash report was from a 162-page file with 20 or so images, all placed from OneDrive, and the issue arose repeatedly with any of those images, using the latest version of Publisher.

For a while I was using the workaround of deleting an image that had got out of place, or needed attention to wrap settings or size/resolution, and placing it again afresh, instead of using 'replace image', but even if I  had saved the file the images would not stay in the right place if I became incautious and caused the file to crash again.

Les

[Callum]

This is a strange one unfortunately the person I need to speak to regarding this is now out of office until tomorrow morning so I likely wont have any solutions or suggestions for this issue until then. If you place an image into your document directly from your computer does this bug still occur?

Thanks
C

[Callum]

Our QA team have asked for the original file if possible could you provide a copy of it? This bug isn't one we've seen before are you able to remember the last actions you performed with this document before the crash started occurring? If you would rather not post your file publicly let me know and I will provide a link to our DropBox

Thanks
C

[lesbillbell]

Hi @Callum sorry for the delay, I thought I would get another email notification of any reply from you but did not.

On 2/23/2022 at 3:41 PM, Callum said:

If you place an image into your document directly from your computer does this bug still occur?

I have just tested this and yes, it does.

9 hours ago, Callum said:

Our QA team have asked for the original file if possible could you provide a copy of it? This bug isn't one we've seen before are you able to remember the last actions you performed with this document before the crash started occurring? If you would rather not post your file publicly let me know and I will provide a link to our DropBox

Thanks
C

Sorry, since it started happening on or before 18 January I have been working with various copies of the original file on an older version of Affinity Publisher I reverted to on my desktop computer. I can still use the latest version of Affinity Publisher on a laptop, that is how I did the tests. I can no longer remember which file I was working with when the crashing was going on. It crashed whichever computer I used, before I reverted to 1.9 on one computer. I know which file I think it was. I struggled to the end of the image editing by deleting and placing images again instead of performing operations on the images that made the program crash. Now, I cannot get it to crash, even though the test file just did. Does the first dump file I uploaded hold the filename? If you give me a Dropbox link I can send you the file I think I was working with, but I'm not sure it will reproduce the crash behaviour now. Odd. At least I can upload the test file. Let me know.

Regards

Les

[walt.farrell]

49 minutes ago, lesbillbell said:

I thought I would get another email notification of any reply from you but did not.

You're not Following this topic (see the Follow icon on the upper-right if you're on a large screen browser, or below the topic if you're on a smaller screen mobile device) and so you'll only be notified if someone Quotes you (as I did) or tags you using an @ sign, like this: @lesbillbell.

[lesbillbell]

Thanks, @walt.farrell , much appreciated!

[walt.farrell]

You're welcome.

 

[lesbillbell]

Hi @Callum you've gone very quiet on this topic. It was by no means solved - I have not dared to use version 1.10.4 of Affinity Publisher any more. You have the dump fille, and I have many more from before that when the same crash occurred over and over. Please update me. I see that version 1.10.5 is out - am I to suppose that has fixed the issue, or don't you know?

Best wishes

Les

[lesbillbell]

@Callum my file imagecrashtest2.afpub still crashes if I try to move the inserted image with version 1.10.5. See dump file.

b94f11cd-2fd3-4e66-91b2-9c9a28fa24f8.dmp imagecrashtest2.afpub

[lesbillbell]

But, @Callum a new file created in 1.10.5 (imagecrashtest3.afpub) does not seem to have the same problem. This is hopeful, but still means I cannot work confidently with older files. Please advise.

imagecrashtest3.afpub