Search the Community

This seems to be a 100% repeatable crash everytime I try and work on a grouped set of objects. I haven't figured out how to continue my work yet, as this crash is blocking me using the file. Process: Affinity Publisher 2 Affinity Store [29096] Path: /Applications/Affinity Publisher 2.app/Contents/MacOS/Affinity Publisher 2 Affinity Store Identifier: com.seriflabs.affinitypublisher2 Version: 2.4.2 (2371) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-05-04 13:31:27.6794 -0700 OS Version: macOS 14.4.1 (23E224) Report Version: 12 Anonymous UUID: 98BB7D5D-E8F4-160D-D341-62A4648C8269 Sleep/Wake UUID: BBFB7362-2DF4-45D6-AF70-971274F4B873 Time Awake Since Boot: 35000 seconds Time Since Wake: 18074 seconds System Integrity Protection: enabled Crashed Thread: 16 Dispatch queue: CA::CG::Queue Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace COREANIMATION, Code 2 function=path_stroke_curve_frag_lph spec=Tps0A3Xhf Function path_stroke_curve_frag_lph was not found in the library Thread 16 Crashed:: Dispatch queue: CA::CG::Queue 0 libsystem_kernel.dylib 0x18a1ab0ac __abort_with_payload + 8 1 libsystem_kernel.dylib 0x18a1d0f08 abort_with_payload_wrapper_internal + 104 2 libsystem_kernel.dylib 0x18a1d0f3c abort_with_payload + 16 3 QuartzCore 0x1926b2b70 CA::OGL::MetalContext::create_fragment_shader(CA::OGL::MetalContext::FragmentShader::Spec const&, bool) + 3968 4 QuartzCore 0x1926b0770 CA::OGL::MetalContext::get_pipeline_descriptor(CA::OGL::MetalContext::Pipeline::Spec const&, bool, std::__1::atomic<bool>*) + 168 5 QuartzCore 0x1926afb84 CA::OGL::MetalContext::load_pipeline_state(NSString*) + 244 6 QuartzCore 0x1926ae53c CA::OGL::MetalContext::draw(MTLPrimitiveType, unsigned int, unsigned int, void const*, unsigned long, unsigned long, unsigned int, unsigned int, unsigned short const*, CA::OGL::ClipPlane const*, CA::OGL::MetalBufferPool::MetalBuffer const*) + 9556 7 QuartzCore 0x1926b7e6c CA::OGL::MetalContext::draw_path_curves(unsigned int, float vector[2] const*) + 92 8 QuartzCore 0x192772cb8 CA::OGL::PathStroker::flush_curves() + 100 9 QuartzCore 0x19277463c CA::OGL::PathStroker::finish() + 52 10 QuartzCore 0x192558520 CA::CG::fill_path(CA::CG::Renderer&, CGPath const*, CA::CG::StrokeParameters const*, CA::Rect const*, CA::ScanConverter::FillRule, CA::Mat2<double> const&, bool) + 3188 11 QuartzCore 0x19261e29c CA::CG::stroke_path(CA::CG::Renderer&, CGPath const*, CA::Rect const*, CA::CG::BasicState const&, CA::CG::StrokeState const&, CA::Mat2<double> const&, bool, bool) + 292 12 QuartzCore 0x1924fc570 CA::CG::DrawOp::render(CA::CG::Renderer&) const + 3716 13 QuartzCore 0x1924f8c74 CA::CG::Queue::render_callback(void*) + 1476 14 libdispatch.dylib 0x18a02e3e8 _dispatch_client_callout + 20 15 libdispatch.dylib 0x18a035ae4 _dispatch_lane_serial_drain + 956 16 libdispatch.dylib 0x18a036544 _dispatch_lane_invoke + 380 17 libdispatch.dylib 0x18a0412d0 _dispatch_root_queue_drain_deferred_wlh + 288 18 libdispatch.dylib 0x18a040b44 _dispatch_workloop_worker_thread + 404 19 libsystem_pthread.dylib 0x18a1db00c _pthread_wqthread + 288 20 libsystem_pthread.dylib 0x18a1d9d28 start_wqthread + 8

this bug makes it impossible to work with the app right now ;-(( steps to reproduce: - open any image - go to layers and add a new layer (appears as first layer) - try to move any layer as soon as you try to move a layer the app crashes ;-(((

Using latest build of Affinity Designer 2 on both Mac and PC. This bug has existed through all versions of Affinity (I've used both 1 and 2) on both platforms. When I use the Set Fill (i.e. click on the black circle here) on a Group Designer completely hangs and I need to use Task Manager on PC or Force Quit on Mac to break out. I lose work to the last recovery save. Obviously, clicking on the group is non-sensical as I actually intend to apply the fill to some object within the group but the program should throw an exception not completely crash. Have been having this problem for years but finally got my but over here to post. Love to see it fixed.

Hi, all 3 of them are crashing on start on my M1 Pro MBP, macOS 14.4.1. Reports attached. Publisher.txt Designer.txt Photo.txt

Hi NathanC, When I make a preset with jpg and webp in the slices export panel and close and open Affinity Photo, then load the preset Affinity Photo crashes still. First I had the idea that it was because of older version presets, but when creating new presets it is still crashing. This bug was reported by me months ago. I attached the export_config.dat again as well as the bug report from my iMac when the crash happens! Back to version 1 again! David affinity-photo-crash.pdf export_config.dat

see clip RPReplay_Final1713859081.mp4

Sorry guys I'am not happy with the leatest version under Windows 11 Using brushes in every sort the system hangs up, or freeze up, Or I need to rmove the crash handler by hand to get the systeem working, or I need to rermove Photo to get my system working. I have the newest windows versions, newest graphic drivers and so more. for the RTX Nvidia 3060 (studio) I use a Intel i7-11700K cpu with 80 Gb ram The leatest beta had and have not this problem. So I don't know what is different to version? Intrest is I have seen this sort problems before 2.4.1 beta was running perfect and the final version gives problems.

If you drag an image (eg: *.png) from a .ZIP file onto a document in Publisher v2.2.1 the application will crash. NOTE: Worked in v1.0. ***Also crashes in beta Publisher 2.30 (2114) MacOS: Sonoma v14.1.1 (23B81)

So I've been using affinity photo V1 for a few years now and everything seemed to be working fine up until a few weeks ago, when I decided to upgrade my GPU from an RX 580 to an Intel Arc 750. Nowadays, whenever I start the program, it shows me the prompt at the start-up but after that, it barely opens the program and it just shuts itself down. I'm frankly not quite sure what the problem is but I can confirm that this issue has not allowed to open the software on my current rig.

I was working on a project and I saved and closed it and then reopened it, changed something and while saving it crashed and from there on every time I change something and try to save, it crashes. I attached the crash report. Hope you can help! 189e5f35-6d6f-4fe8-ad36-5d111f8fba79.dmp

Dear team and members of the forum, please help! Every time that I use the Affinity Publisher 2 on my computer it keeps crashing. I have used the Affinity Publisher version 1 without a problem, but it started crashing when triggering several functionalities (as saving, exporting, fonts, etc) with the updates after that. Totally useless. So, I upgraded to version 2 with hope to stop the problem, but I am facing the same problem, especially when activating the undo function. Probably I will find more problems with this version as well, but I am so tired of not being able to work with affinity that I need some proper help. Here is a video where I explain the problem, but for some reason loom didnt record the crash itself. I frost the last image of the app before it happen. https://www.loom.com/share/7ce06c640cca4118a6cd5b25136515ad?sid=8210f06d-017b-4610-b4cd-13ad1f117247 Here is what I have tried already: - I am using the new version of AP2 - 2.3.1 (I have installed it yesterday), despite I have crashing problem with APV1 (except when I used the version 1.10.4, but it doesnt have the features that I need) - Turned off the first three option when clicked the ctrl key during the launch, - Hardware acceleration was already turned off - Unistalled all problematic updates in windows 10 and 11 identified in other posts of this forum. Now, I have basically none windows update, what is not safe at all, right? - I installed the last version of .NET (8.0) from the link you have provided above - I checked the firewall but it seems that it is not blocking the app. - I have no idea what to do now. Please, help! I upgraded to AP version 2 to see if I could stop the crashes, but I cannot work at all with it as well. Please, find attached the crash reports p.s: bare in mind when send some support that I dont understand nothing about coding or technical computer stuff. So, I appreciate to send instructions in the more clear way you can. Thank you in advance 356307cc-ccde-42d5-bc95-78e3e9589171.dmp 7457a752-8ce7-4e7f-af4a-e109174e0bcb.dmp aaf74613-4e03-4453-ae7d-7de52a2f7d47.dmp ff6236d2-803c-4f38-be08-aa7d0d081dca.dmp 76f65e27-db91-48c6-a51a-5bc26c7616b9.dmp a62af3fe-2109-40ff-8443-454c1a8069ca.dmp

I'm not having any success recovering a file after AP v2.3.1 crashed. I'm on a 2017 MacBook Pro, Ventura. I never saved the file, but I had it open for at least an hour. I usually save more often, but I was experimenting with some techniques, so I didn't save it at all this time. I started with a DNG RAW file, opened it in the Develop Persona (RAW Layer linked), then did a lot of work on it in the Photo Persona. I have my recovery time in Settings set to 300 seconds, but I couldn't find any record that autosave ever saved my unnamed file anywhere. I looked in ~/library/application support/affinity photo 2/autosave. Nothing is listed there from today.. When relaunching AP, it asked if I wanted to recover the file and I said Yes. It opened the original DNG RAW file in the Develop Persona, which was useless to me. Shouldn't autosave save a copy every 300 seconds, per my AP Settings (preferences)? Is there any way to recover this file? If so, where do I look and how? Thanks.

Hello! I had this problem at least twice now, and want to report it. When using the brush repeatedly, while having pen pressure on, affinity designer freezes and crashes, after a few quick brush strokes. I tried it without the pen pressure and it works fine without it, i think. Only setting I have changes i that I disabled Windows Ink inside of Affinity Designer and on my tablet. I don't have any issues with pen pressure on Affinity Photo, so I personally think the vector brush tool in Affinity Designer with pressure sensitivity ON is just bugged. Hope you can reproduce this problem and fix it. Thanks for your time and patience! Extra Specs, just for good measure: GPU: RX Vega 56 CPU: Ryzen 5 3600 CPU Graphics Tablet: Huion Inspiroy 950P. RAM: 16 GB of something. affinitybrushbug.mp4

What Application are you using? [Publisher] Are you using the latest release version? Yes 2.3.1 Can you reproduce it? Yes Does it happen for a new document? Yes If not can you upload a document that shows the problem? See Attached File If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following: What is your operating system and version MacOS Ventura 13.6.4 Is hardware acceleration (in Preferences > Performance) ON ? (and have you tried the other setting?) NO What happened for you (and what you expected to happen) Provide a recipe for creating the problem (step-by-step what you did). Create a new document using custom page settings of 4.9x6.9 Create a table on the 1st body page (see attached file) Copy that table and then paste it on the Master page When I did that the table size changed to a smaller version of the table. Click on the table to select it. move the cursor to the bottom circle to resize the table. When you click and hold on that circle, the application crashes. Screenshots (very handy) or a screen capture/video. No Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers. NO Did this same thing used to work and if so have you changed anything recently? (software or hardware) I did not have this issue in Version 1 when I first created a file like this. 2024-01-30 Publisher Crash log.txt Large Format Shoot Log.afpub

Affinity Designer V2 Crashes - When I click on the Recent Files button in the startup window. It works fine if I go to File > Open Recent Is it a common issue/known bug? I noticed that it's happening in Affinity Photo also, haven't tried it with Publisher yet. I am on Windows 10 and Using the MSIX installer for all.

I'm having an issue when exporting a (not very complex -- less than 20 layers, I think) 600 dpi 33x50 inch Designer project (created entirely in this version of Affinity Designer) as a 16-bit tiff and it crashes if I don't hit the export button fast enough. It crashes right when the "calculating size" message gets to 100%. The tiff seems to get created okay if I hit export before Designer finishes calculating the size. Creating a similar project with the same dimensions and dpi, with one blank layer doesn't seem to cause a crash. I accidentally selected the HDR file type during export at one point, and this same project also crashed the app with that file type as well -- right as it finished calculating the size. Latest version of Designer 2.3.1 Hardware acceleration setting doesn't change the outcome. macOS 14.2.1 M1 Max 64GB RAM >3TB free drive space.

Platform: MacOS 12.6, Apple M1 Max processor, 32 GB memory. To reproduce: Open an image (stock image is fine). Add live adjustment layer - exposure. Add live mask layer (Luminosity). All works fine to this point, changing mask and exposure. Now, try sliding mask layer down (click, drag downwards, blue line appears between exposure and base levels). Result - crash. Reproducible. Every time. crash-report.txt

I am using Affinity Publisher v2.3.1 Steps to reproduce: Open attached package document in Affinity publisher (the original document is created in Affinity Design, I was using Publisher to get the text flowing between the boxes and adjust hyphenation, etc). Select the first text box in the right art board. Next, click into the text box to edit it. Begin holding the Shift key, begin selecting text using the down arrow. The application will crash as soon as you select the second to the last line of text. It seems to be fairly reproducible on my machine, but a couple of times, when trying to record the video, it didn't crash. Maybe recording the video had to do something with it. I can't say for sure. It seemed that maybe being zoomed in such that the next text box, into which the text would flow, was not visible may have had an impact on the crash, or at least more reliably reproduced it. Hopefully, this info is helpful. In the zip is the afpackage file, the fonts and image that are used in the document. There is a full system information dump text file and I also included a few crash dumps from affinity crash report folder under the user profile. There is also a video showing the crash. Please note that the image included is not public domain, and the text is copyrighted, so it is fine to use for debugging, but should not be used in any advertising, publication, demo, etc. It is being included here solely to assist the developers in reproducing the problem.

Hello there! I have created a 150 pages photo book in Publisher 2.3.1 on my iPad Pro (M1, 256 GB (8GB RAM)) and would love to export it to a PDF file so I can share and later print it. However, whenever I try to do that, Publisher gets to about 50 % and then crashes. I tried splitting the file into two 75 pages documents and those can be exported properly, even though this also takes FOREVER. I know it‘s probably just a very very huge project for Publisher – but shouldn‘t it be able to cache the files somewhere on the iPad‘s local storage so even with the limited RAM the iPad should be able to handle this? In general, PDF exporting with a lot of images takes sooo long. It‘d be great if Serif could speed this up. In addition, it would be super great if I wouldn‘t have to create a separate file for this split-export: Why is there no option to select specific pages on the export dialog? Thanks in advance for any feedback!

Hi support, it looks like I found a - now more or less reproducible - issue with the index in Affinity Publisher V2.3.0. With three (bigger) documents I created, I very often get a crash to desktop (no alert or anything) just after loading them (normally about the time the auto-correction has just finished underlining wrong words). I'm using the German UI (but I have had the same crash when using the English version, too, so I guess this is not really relevant). All three documents have in common that they have an index. I've created a new document with some filler text to try it out, and it crashed Publisher basically every time I load it. I have attached it to this post. I can often prevent the crash with my bigger documents if I'm fast enough to click the "Update index" button (in "Index" studio) before it has finished rendering after loading (even though it doesn't work reliably with the below test document), which seems to point at some issues with the index itself. This bug is really annoying, especially when you are just loading a second document to check something in there, only for Publisher to crash, and as such losing your work since the last save from the document you were working with at that time you loaded the second document! Can you please have a look and get this fixed (I have this problem basically since V2.1 already, but couldn't easily reproduce or pinpoint it. I think it worked with V2.0 without issues, if I remember it correctly). My system: Windows 10 Home, 22H2, build 19045.3803 Hardware acceleration setting doesn't change anything, it crashes with enabled and disabled. 16 GB RAM, SSD Harddisks AMD Ryzen 5 2600 Six-Core Processor 3.40 GHz NVidia GeForce RTX 2060 (6 GB) I have a small Adesso tablet connected, but don't use it for Publisher I have an Elgato Stream Deck (15 key version) connected as well, but again don't use it for Publisher Index-Issue_Example.afpub

After installing the last update of AP, I noticed that AP sometimes crashes while it is inactive for a while: AP was hidden or the AP window was minimized (I use Stage Manager) then. macOS 13.6 I attach the last genenerated crash report. I have a few more Affinity Photo 2 Affinity Store-2023-09-25-172356.ips

Device name: Surface-Laptop Processor: 11th Gen Intel(R) Core(TM) i5-11300H @ 3.10GHz 3.11 GHz Installed RAM: 16.0 GB (15.8 GB usable) System type: 64-bit operating system, x64-based processor Pen and touch: Pen and touch support with 10 touch points Edition: Windows 11 Home Version: 23H2 OS build: 22631.2506 Experience: Windows Feature Experience Pack 1000.22677.1000.0 Problem as per title, the program is unusable. Things tried - multiple reinstalls, resetting the app, CTRL when starting (crashing then too). Happens on both my main computer (Win 10) and laptop (Win 11). Happens in version 1 and version 2 including the customer beta version. Searched for crash logs but none in the user folder under Affinity/crash logs. Just hangs for about 5 seconds then disappears. What is the refund policy? as it is utterly unusable.

I have the same issue, it'll start and then crash like a few minutes later. It worked fine before but now it's just crashing like crazy. Edition: Windows 10 Pro Version: 23H2 OS Build: 19045.3570 Device Name: Alienware 15 R3 Laptop RAM: 16.0 GBs/(15.9 useable) 64 bit OS.

This is a problem already reported on the windows side, but I have confirmed it is also an issue on Mac in v2.2 in Designer. The linked post also claims this is an issue in Photo also. Here is my post on the Windows forum: I can confirm this is an issues on Designer v2.2.0 on Windows. I don't recall this being an issues on previous versions going back to v1.8.5. I can recreate this issue consistently on my computer with the same behavior...dragging a swatch onto the node on the gradient as pictured by the OP. Freezes Designer then crashes. I am able to work around it by selecting the node first then just clicking the desired color in the palette, but that is not as intuitive. My co-worker is able to reproduce this as well on his Windows machine as well. I just tested on my Intel 2018 Macbook Pro running Big Sur 11.4 and I can confirm it is an issues on Mac as well. I had no issues on the previous version 2.1.x, then I ran the updater and tried again and it crashed. I haven't had a chance to verify this on my Apple Silicon Mac yet.

“Fill tool” is doing multiple fill actions by just scrolling/browsing the “Fill Type” carousel. It’s creating multiple history states by just scrolling the “Fill Type” option and sometimes causing a slow down and even a crash! I’ve attached a video demonstrating the bug, notice the “history studio”. Restarting the app didn’t help! Affinity Photo v1.8.6 iPadOS v14.0.1 (iPad Pro 11 inch 2nd gen) IMG_0903.MP4