Jump to content

Recommended Posts

  • Staff
Posted

Welcome to the forums @Gorgons Grimoire,

When this occurs are you attempting to delete multiple pages simultaneously, and if so does the same crash happen when it's just individual pages that are deleted?

Additionally, could you provide a copy of a document where you've encountered this to see if it can be replicated, along with a recent crash report file from when this last occurred? The FAQ below details how to find crash reports. If you do not wish to share the .afpub file publicly I have provided a private upload link below.

Upload link: https://www.dropbox.com/request/eoHvOForDhVupVvvZ0hL

Many thanks

  • Staff
Posted

Thanks, if it's not producing any crash reports then it sounds more like the app is going into an unresponsive or frozen state when you are deleting pages, and the app is subsequently being manually force closed rather than crashing on it's own.

With both docs open in Publisher I've not been able to re-produce any crash or app hang on any device so far, even when deleting hundreds of pages at once it only took a few seconds. With the documents being this large they are quite RAM heavy, I'd recommend trying the below:

- Reboot your device and limit the number of background apps you have open to only Publisher, and then open one of these documents and after a minute try removing a few pages.

- Disable the Hardware Acceleration checkbox under Edit > Preferences > Performance, once unticked close the interface and restart when prompted to before trying again.

- If the app still freezes following a page delete, open Windows Task Manager and check your current Memory usage level in the Performance tab to see if it's at/near maximum, and leave the app a few minutes to see if it recovers and deletes the page.

  • Staff
Posted

Thanks, since you've got the app to crash on 'Libstory.dll' i'm wondering if there perhaps is a crash that could be replicated from your document when removing a certain set of pages, if you were to go in and delete the same set of pages again, does the same crash occur? If so, could you possibly provide a screen recording demonstrating this? I've provided a link to the screen recording FAQ below.

Many thanks

  • Staff
Posted

Hi @Gorgons Grimoire,

Thanks, I had originally been only deleting double page spreads at any one time, but I had not considered that deleting single facing page causes the pages to re-flow across the entire document which then triggers the crash. I can now replicate your crash on both documents every time.

After a discussion internally with the QA team we believe the crashes in your document are related to the single facing page masters applied at various points throughout the document, they are tripping up the app when the page content gets re-flowed as it's trying to preserve the masters, so I'll be getting your files logged with the developers for further investigation.

Since it's the masters that are triggering the crash, we've found that it is possible to clear the existing masters by creating and applying an empty master to all pages, setting it to 'replace existing' and the content set to 'Migrate' which Promotes the layers to just regular objects, there might be some adjustments needed following the application and it's really not an ideal/great workaround, but it will allow you to delete single facing pages again.

  • 9 months later...
Posted

I know this is an old thread, but just wanted to flag that this happens to me regularly. Currently using latest build on Mac (Sonoma, all updates). It's happened on every build of Publisher for well over a year. I haven't flagged it before because it's pretty random – sometimes it crashes, sometimes it doesn't. Always when deleting a page though. I've just learned to always hit Save before trying to delete a page, but it's not idea. Sometimes it's just impossible to remove a page.

  • 1 month later...
  • Staff
Posted

The issue "Deleting single facing pages causes an app crash due to the presence of single facing page masters- File(s) specific" (REF: AF-1276) has been fixed by the developers in the latest beta build (2.6.0.2831). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

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.