Gianni Becattini

Here are two videos of the problem. If I don't open the files and wait 20-30 seconds, no problem. Registrazione schermo 2025-01-17 alle 19.24.46.mov Registrazione schermo 2025-01-17 alle 19.26.47.mov

Yes, sorry. I forgot to say something important. The problem is somehow connected to the TOC. I will do some tests so that I can be more precise.

Probably this is also present in the production version, I remember I often noted it. When you open a rather complex book, you have to wait that everything "settles" before trying to open a chapter. If you do, almost every time it starts trying to renumber pages and there locks. You need to kill APub.

I am rather sure about it. On the M2 I have no problems.

The latest beta. I can make a video, if it helps

Sorry, in my case the problem is still there. It was the first thing I checked. OK on M2, fails on Intel.

Thanks for answering. I am uhm... a "kind" of teenager now. They say that from a certain point we go back... 😬

No, I dont't think so, but for me memory... uhm, is a BOLD word! 😃

👌

These days another book of mine has been printed on real paper; for a simple enthusiast like me it was a big satisfaction seeing something with such a quality like an art book. All that would not been possible without Affinity and, above all, without the help from this community, that I believe is the most valuable part of the suite. I am completing another book, and I added a thank you to all of you, as you can see below. BTW, my books are really complex from the Publisher point of view, because I link directly hundredths of Photo images, with dozen of layers, so my satisfaction could be partly also developers' satisfaction; probably, just one of my books can be considered a good benchmark. Many years ago I was a software developer too and can understand their problems even too much. So a big thank you also to them.

Thanks, Mike. In my experience the problem is only on Intel platform, with M2 everything is OK on my side. Most of my problems were in someway connected to this bug, but, as you probably know, it is easy to go in a mess before understanding it. For example, in one of the crashes, a file was damaged, and that misled me completely. But eventually, the problem was there again. For the rest, I didn't find anything like a bug until now in 2.6 (apart from the terrible style confusions in TOCs, but for it there is a working workaround).

Today I had a separate confirmation of the bug, working on another file. I lost several hours to arrive to the same conclusion: tables makes Publisher crash on export (already in preview, you have not to confirm). Sometimes the preview remains running, sometimes it crashes the application). I attach the file. There are two large tables on the last pages. Removing them, the export succeeds. 7KS 02 Story (styles master).afpub

As you can see from this thread, in October 2023 I could use it following a suggestion from MikeTo and Anto.

Thanks for answering. I created a new document and imported the pages from the old, removing thus all the masters. It works. My problem was due (also) to my dumbness, because the very many MPs were in the document that I used to sync setting, styles and so, and thus they reappeared every time. I am woking on one (old) of the first books I created trying to make it clean and well organized. Nevertheless export is always a nightmare, and every time I experience new crashes. Removing chapters or parts of them, I could often find what was disturbing, but I believe that Affinity should work on this point. I saw many improvements in stability, but we are far away from an acceptable situation. Yesterday I found what I believe is a bug (the first line of the tables). Today there is again something that determine the application crash. It would be great if Affinity had at least some log file to understand where the problem arises.

No, there was formerly. I used it on Mac. The only way to remove master pages in group is as Mike suggested to create an empty document and import.