Vaclav Slovacek Posted November 11, 2022 Share Posted November 11, 2022 Hello, I hoped Publisher 2 would also fix stability issues. However it crashes constantly when opening a document. Lets hope some effort will now go to stability and bug fixes. The error log is attached to this post. publisher-2-error.txt Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 11, 2022 Staff Share Posted November 11, 2022 Hi @Vaclav Slovacek, Are you able to attach a file so we can look at this further? You can use this link to keep it private Thanks Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 12, 2022 Author Share Posted November 12, 2022 Hello Jon, I have uploaded the files that are embedded in the crashing Publisher document. As the uploaded Designer file is also crashing I have just uploaded that one as a package. I suspect that the uploaded document is the root cause. Thank you. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 14, 2022 Staff Share Posted November 14, 2022 Hi @Vaclav Slovacek, The afpackage and afdesign files inside are all opening fine for me, can I double check it's those files that crash on open for you? One of the afdesign files has a linked resource I am missing so I'm wondering if that is part of the reason I might be able to reproduce it. Can you remove the afdesign files from the package temporarily and see if that opens for you? Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 It does not crash. When I tried it before sending it crashed, but maybe a document in another tab was the cause when I am thinking about it. 2 hours ago, Jon P said: Can you remove the afdesign files from the package temporarily and see if that opens for you? Do you mean removing the linked document from the Publisher file using it? Or switching it to embedded? Not sure why the linked file is not included in the package, seems Affinity does not include nested linked files in the package. Just to clarify I have this structure: Publisher Document A, contains Designer document B, which contains Designer Document C. This is intentional as it helps to reuse resources and propagate the changes from Document C. Do you want me to remove usages of Document C from the Document B? And then try if the document A still crashes? Linked documents are a great feature on the paper, but to me it seems Affinity has issues with it. Are nested linked documents supposed to work or it is a known limitation that they cause issues? It seems these issues arise when doing anything more complex. Is there any way to provide/enable more detailed logging? Also does it make sense to send crash logs from the macOS dialog via "Send to Apple"? Do you guys receive those? Quote Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 Not sure this is related to the issue (probably not). But on crash if I Reopen Publisher the macOS Terminal opens with the following text: Last login: Mon Nov 14 14:41:57 on ttys018 /Applications/Affinity\ Publisher\ 2.app/Contents/MacOS/Affinity\ Publisher\ 2 ; exit; (base) REDACTED ~ % /Applications/Affinity\ Publisher\ 2.app/Contents/MacOS/Affinity\ Publisher\ 2 ; exit; 2022-11-14 15:01:01.338 Affinity Publisher 2[17448:1888471] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2022-11-14 15:01:01.338 Affinity Publisher 2[17448:1888471] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug. 2022-11-14 15:01:01.365 Affinity Publisher 2[17448:1888471] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2022-11-14 15:01:01.509 Affinity Publisher 2[17448:1888471] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0xaa03, name = '6LVTQB9699.com.seriflabs.ipc.release2.server' See /usr/include/servers/bootstrap_defs.h for the error codes. 2022-11-14 15:01:04.104 Affinity Publisher 2[17448:1888471] Failed to select item with enum value -3! 2022-11-14 15:01:04.107 Affinity Publisher 2[17448:1888471] Failed to select item with enum value -3! 2022-11-14 15:01:04.108 Affinity Publisher 2[17448:1888471] Failed to select item with enum value -3! 2022-11-14 15:01:04.268 Affinity Publisher 2[17448:1888471] Could not find image named 'chainlink'. 2022-11-14 15:01:04.268 Affinity Publisher 2[17448:1888471] Could not find image named 'chainlinkconnected'. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 14, 2022 Staff Share Posted November 14, 2022 Quote Is there any way to provide/enable more detailed logging? The crash report is the best we easily have access to, and that seems to be pointing towards an issue loading a linked resource. I was wondering if removing any of the linked documents before opening (so they then appear as missing, and can be re linked) would fix the issue on your side since I'm not getting any issues opening the files you attached. Nested linked documents should be fine, we have had a few issues in the past that have been hard to replicate that are similar to this, when we are sent the files to investigate we can't reproduce the crashes happening. Previously breaking and restoring the links has fixed those few issues for customers Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 So what is the best way to break the link? Rename the linked document? Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 14, 2022 Staff Share Posted November 14, 2022 Yes or move it to another place, I should have clarified that! Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 Is there a way to tell which of the linked file causes the issue? I am having the issue right now in a document that has 20+linked files. Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 14, 2022 Staff Share Posted November 14, 2022 I'm afraid not, but if all the linked files are in the same folder, you can rename the folder and that will break the link to all 20 files Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 OK. I will play with this and check if that helps. I have feeling it might as the frequency of this issues grow over time up to unbearable level as the documents get "older". I have tried to use "Save As..." as people mentioned it might save "cleaner" file than the regular "Save". However that doe not seem to help. Is there any tool/process to somehow check whether the files are OK? If this is not fixed in the next minor/bug-fix release it would be good to have at least some more logging around this feature or a way to provide more details about it back to Affinity. It is an issue spanning from 1.x era and I really hoped this would get resolved in the next major version. It really makes it difficult to use Affinity productively. I really want to love your products because aside stability they are a great package. Quote Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 14, 2022 Author Share Posted November 14, 2022 I have renamed the folder with the linked documents. Then relinked. Publisher has not crashed so far (cca 10 minutes). Before it happened within 1 minute after opening the doc. The CPU usage after relink is very high - hundreds of percents. Whatever Publisher does in that process seems to help. Will update this post when I experience a crash again. Quote Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 15, 2022 Author Share Posted November 15, 2022 Hello Jon, just confirming that the trick with renaming the folder and relinking in Resource Manager helped so far. No crash since then after several hours of work. I still hope this gets resolved though. MikeTO and Jon P 1 1 Quote Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 19, 2022 Author Share Posted November 19, 2022 Just so this is not forgotten the above workaround seems to be very short lived. Getting crashes again and again. Doing the trick with moving thing around but with gorwing complexity of the document it seems to diminish very quickly. Attaching error log from one of the crashes. Although I am losing hope that Affinity will resolve this in foreseeable future. publisher-error-3.txt Quote Link to comment Share on other sites More sharing options...
Vaclav Slovacek Posted November 19, 2022 Author Share Posted November 19, 2022 Attaching archove from the Diagnostics folder. Hope that the number of reports might help to find the root cause and demonstrate the atrocious experience with Publisher. Crast Reports.zip Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted November 23, 2022 Staff Share Posted November 23, 2022 Hi @Vaclav Slovacek, I can continue to look into this and see if I can reproduce a crash. The package that you sent contains links to an afdesign file, which links to another afdesign file (Atlas Resources) which I don't have, could you upload this document (and if it contains any links itself, those documents) so I have access to all the files being opened, hopefully then I might be able to reproduce the behavior so we can investigate this issue. Looking at the crash report, it seems to be struggling to load a linked PDF resource which I can't see in the files I have received Thanks Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Staff Pauls Posted November 29, 2022 Staff Share Posted November 29, 2022 a lot of the crashes are preflight related turning that off may result in fewer crashes although an underlying problem with resources may still exist. Quote Link to comment Share on other sites More sharing options...
kai2 Posted November 30, 2022 Share Posted November 30, 2022 Hi, I also have this problem with an older document. I am attaching the report. Is it not possible that it is a font problem? Regards Kai-Uwe error.rtf Quote Link to comment Share on other sites More sharing options...
Staff Pauls Posted November 30, 2022 Staff Share Posted November 30, 2022 You'll need to provide the crash report from the console app. Please make a new thread for us to investigate Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.