Search the Community

Publisher 1.8.3.641 crashes multiple times (5-8) before it will stay open. Win10 on desktop. Then almost always crashes or freezes when opening files. "Open recent files" rarely opens anything and when I click on that I am virtually guaranteed I will have to kill the program in task manager. Eventually it settles down and I can work, but this is unacceptable. Is there an update?

Affinity Photo crashes as soon as i try to load a photo. I need some help sorting out why. I am running on latest release of Win10 Pro with 32GB memory on an i7 SSD program drive with 325GB free and Data drive with 1.13TB free. I run Lightroom, Photoshop, and Blackmagic Resolve with NO issues. So cant see why Affinity Photo should be having an issue. Hope someone helps...if im posting in wrong area please let me know...new to Affinity Software. I had high hopes for Affinity Photo

I create a new file, create an empty white layer, attach a live filter to it (Simple Perlin Noise), duplicate this layer, and it crashes Affinity Photo. Crash dump is attached. a34081f7-5dd7-4869-93de-a6c05c8f0127.dmp

Hi Chris, The app is crashing when importing files over the network, please see the video attached. I guess it would help to to use smaller buffer chunks and have better error control when copying the file over. Cheers! Videoleap-F9F0F6FD-218C-44A3-87D2-2F95DBDAF21C.MOV

When I tried to open a very large hi-res TIF photo posted from NASA, the Affinity Photo GUI opened but after 15 or 30 seconds the program crashed and closed. At first I thought the file may be corrupt, but it opened in GIMP without a problem. I tried 3 different times to open the file in AP and each time the program shut down and sent me back to Windows 10. The file is hi-res, contains 1.8 billion pixels, and has a file size of 2.25GB. Is there a limit to the size of files Affinity can open? Hardware specs: CPU - AMD7 2700; GPU - MSI NVidia GeForce 2060 Super; RAM - 32GB

Hi Forum, I'm quite desperate. Thursday I contacted affinity@serif.com and have not received any feedback yet. Maybe I have to "apply" for support via this forum. Unfortunately I can't find out on the website of Affinity how to behave if publisher obviously has a problem or maybe a bug. With both Files, short time before there was no problem with working on it in Publisher. Than in the first File, Affinity Publisher has crahed immediatelly. Then no way to reopen the file without crash the Publisher again and again. I restart the MacBook many times since the problem. No change. In the second file, while working Affinity Publisher has freezed by changing some Link-Stuff. I had to close the application with TaskManager... Than no chance to reopen the File with Publisher without a crash, again and again.. So here my Bug-Report: Are you using the latest release version? YES => Affinity Publisher 1.8.3 Can you reproduce it? YES => Everytime I open the file, Affinity Publisher will crash! Does it happen for a new document? If not do you have a document you can share that shows the problem? With new document => no problem | With 2 documents I can share there are this problems. No chance to reopen the files. Also when I use Time-Machine Backups, the same problem APulisher is crashing imediately... 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 (Windows 10, OSX Mojave, etc)? Mac OSX Mojave 10.14.6 (18G5033) What happened for you (and what you expected to happen) APublisher is crashing every time when I like to open one of the 2 files. > Should open the File and I can work on the documents, like before. Provide a recipe for creating the problem (step-by-step what you did). Double-Click on the File => crash! Or: Open APublisher and click on «File» there «open...» select one of the 2 files, click «open» => crash! Screenshots (very handy) or a screen capture/video. have Bug-Reports (from popup window after Affinity Publisher is crasched). Can also send you the 2 original Files (have done with one Thursda<, 4. June 2020 18:33, no answer still now) 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 new or updateded in Hardware) Did this same thing used to work and if so have you changed anything recently? (software or hardware) (No changed stuff, only change some document-settings in Affinity Publisher => in first file | and did some Link-Text change in the second File) Should I post the text files with the debug contents here? Or do I have to ask for a Drop-Box link? (found some entries for other bugs with this approach) I can also share the two files. But because they are customer projects I don't want to post them directly in the forum. Does anyone have an idea if I "have to" report such problems here in the forum? Is my way the right one? Or is there a better approach to get help as fast as possible and to continue working? I already had a similar problem in February this year. At that time, I got help via the support email (see above). Probably the procedure has changed a bit, because of the ammount of customers... Thank you very much for your feedback. Martin

I'm experiencing persistent crashes while attempting to clone part of one image to another. I'm running Affinity Photo 1.7.1 on a 2018 MacBook Pro 15" with macOS 10.13.6. Here is one of the crash logs: Affinity Photo_2019-08-06-172523_RRL-MacBookPro15.crash. I'm trying to clone Ina, a colleague, out of Ina.tiff and replace her by the bench in No_Ina.tiff. So, following @James Ritson's tutorial (for 1.6, https://player.vimeo.com/video/192599318/), I enter the latter as a new source in the Sources panel, double click it there, choose the cloning tool and option-click on a common point in the two files. Then I go to Ina.tiff, activate the cloning tool, and click No_Ina.tiff in Sources. Now I run into a first problem: the preview of the cloning brush is practically useless, as only bright spots of light appear when I hover over some part of Ina.tiff. Taking a chance on where to place the cloning brush, I click-drag. Soon after I finish, Affinity Photo crashes. The other problem I have with cloning in this way is, I don't seem able to clone from one pixel layer to another in the same document, let alone between documents. Why not? The history for this is, I first developed the a RAW file to produce the Background layer of the document with Ina, then found I had another RAW file that I hadn't intended to develop with just the bench. So I developed it, then copy-pasted it into the document that I was working on in hopes of being able to just clone between the two Background pixel layers instead of having to export both and, I assume, lose the advantage of developing and working in 32-bits. Affinity Photo_2019-08-06-172523_RRL-MacBookPro15.crash No_Ina.tiff

Hey. I am having a similar issue. I am just trying to add pages to a document, but every time I do Publisher crashes with no recourse or explanation. The files are simple and were made with Affinity Design before I bought Publisher. I managed to add the 1st 16 pages, but the 17th crashes it every time. Thoughts?

Start photo, load an image, make a marquee selection, hit Q to enter quick mask mode now hit V to switch to move tool to modify said mask, now click CRASH!!! it happens regardless if you load any kind of image or even if you create a new blank document & it only crashes if you click inside the selection, if you click anywhere else it doesn't crash. same things happens inside photo persona of publisher. NOTE: I'm not attaching any pics or videos as I already confirmed this with a few users & they all reported the crash in exactly the same manner

1.8.3.641 - WIN 10 latested updates - clean new reset of PC and therefore new installation of Affinity Photo. NVIDIA GTX 650 - newest driver 446.14 EIZO CS 2730 Also installed: Affinity Designer 1.83.641 + Affitity Publisher 1.83.641 and Capture One 13.1.0.162 (all downloaded today). --------- Hello, I'm new to the forum and didn't really find a similar problem description on Google. Therefore I'll ask here: When I open an image in Affinity Photo for the very first time via "File -> Open..." it often instantly crashes. When I retry with the same file at the same source there is no problem anymore. I first thought it had something to do with the fact, that the images are on a OneDrive directory (already downloaded before), but now, on my new clean system, it also crashed 2 times with local only images. Now, after approx. 10-15 tries with other files and sources, it works well. But I am afraid it will happen again when I do not expect it. I use DNG from Ricoh GR 3 and CR2 from Canon EOS 6. Strangley enough a have the same behaviour on my iPad Air 3 with the latest Affinity Photo App when I use "Import from cloud" and open files from OneDrive. Does anyone have an idea what can be the reason? I have not experienced such a behaviour in version under 1.83. Thank you very much in advanced. Best regards.

90 day trials of Photo and Designer won't launch on my Windows 10 desktop. I've tried re-installing and restarting. I've reviewed the threads regarding 3rd party software issues, I don't have any of these on my system. I updated my NVIDIA graphic card driver and took the steps to force start for a dedicated GPU. None of these steps have worked, apps freeze on splash page and don't launch. Crash report is attached, any suggestions appreciated. I was really looking forward to trying these. Thx. 751ccbad-e343-4a28-89fd-4bacadd3f127.dmp

My publisher crashes when I try to move a page. It is a 4-paged flyer (to which I added a 5th page as a workaround for the crash, which I cut again on export to pdf). When I grab and move a page up, Publisher crashes without a notice, just closing hard. This can be reproduced. A crash report to Apple is created, I have a copy. Plus I have a screen recording on video, if this helps. The project file can be uploaded. MacOS and Serif Suite are up to date (Catalina 10.15.5, Publisher/Designer/Photo 1.8.3), MacBook Pro 15", 2019, CPU i7, GPU Vega 20, 32GB. I have read this thread ( https://forum.affinity.serif.com/index.php?/topic/116386-publisher-repeatedly-crashes-when-i-try-to-move-a-page/ ) but can't apply a solution to my project, since I do not know how to isolate the problem.

After opening my Publisher program and my file (with a lot a linked pictures) I try to open the Resource Manager. But my program crashes all the time without any warning. If I open the Resource Manager in another file and after this leave it open, close this file and open my file with the pictures it takes a while, but it works and does not crash. If i put a new picture in my "Picture file" and after it open the Resource Manager, it also works. I think it a great idea to have the Resource Manager docked, so I can leave it on the screen. If it is already there, I have no problems! Thank you!

I’m having a hell of a time with Affinity Designer crashing on my iPad. It was fine to start, but now a month later, it crashes multiples times a session and saves at random points. Is anyone else experiencing this?

A while ago, your team "fixed" one of my documents that had some "index" problems. I thought your 1.8.3 Publisher had fixed that problem. I don't know if it is the same problem, but I would appreciate it if I might ask that you (Serif) look at the document to see if it can be repaired. It was created with earlier published versions, and then transferred to 1.8.3. However, in the end, this document somehow became corrupted while in 1.8.3 - now if you do anything after it has opened (edit text, save as, move a frame, etc.), it crashes within seconds. I can easily include a Mac crash report too if needed. Would it be possible to upload the document to your secure DropBox site so you can have a look? Thank you - and Santé -=mark=- OSX 10.15.3, AFPUB 1.8.3

IPad designer and photo. I created some patterns to use in my designs, for the printer I want tocopherol it into a A4 document. So I copy the artboard that holds the pattern and copy it into a new document, when I paste it the program crashes. If I save it to the cloud and open it in photo same thing happens, direct crash. even when I open it on the computer in Affinity photo, it has real difficulties with the file. Anybody any idea henk

I was experimenting with batch converting arw to jpg on about 10 files with different parameters (with or without "convert to sRGB macro, pixel format default, rgb, cmyk, embedded sRGB profile). Anyway, I decided to output around 118 images that I'd already successfully output with sRGB macro/embedded profile, and I think rgb pixel format (maybe left at default). Importing in the same dir where I recently deleted a 10-file batch. parallel checked. The batch job spun up and got to "saving" on the first 24 images but never made it past that. CPU hung out high for about how long it would take to save them then went to idle but the gui still says "saving". I was writing to a NVMe SSD. The drive is not full. under task manager Affinity photo beta is using 29GB (I have 256GB) and barely any (less than 1/2%) of CPU (712 threads). There's another process - crashpad_handler.exe at 0% cpu (6 threads). Been this way for maybe 20 minutes now as I waited, then started writing this. Nothing in event logs. From looking at the thread handles in Resource Monitor it looks like maybe it's trying to write crash info. I attached a txt file with the copy/paste of the handles from Affinity Photo and Crash Handler. System Info: Win 10 Pro 1909 build 18363.836, 256 GB RAM, 2x EVGA RTX 2080 Super GPU, AMD Ryzen Threadripper 3960X 24-Core (SMT off), ASRock TRX40 Creator mobo Affinity_beta_CPU_Handle_Dump.txt ---EDIT--- As a followup, I can't even reproduce what I did to successfully output images in batch. I can do little batches now, but haven't been able to reproduce the 118 image batch - I keep hanging. Have tried all sorts of color profiles and combos of clicking JPG/macro options. have also tried DNG/ARW. Haven't reset my pc yet but that's next. Also tried to do batch in non-beta and had the same hang. --EDIT-- rebooted and still cannot find settings that successfully generate a 118 image batch (except turning off parallel processing). The first one I did worked in parallel (accidentally left box checked to generate affinity format photos and had to delete them) but I tried that too and it didn't work. -EDIT- I did some more tests and things work fine with parallel processing up to 20 images, break at 22. When it breaks the CPUs stop running sooner than when it works (with message saving jpeg... and spinning wheel). I have no idea why I was able to make it work for a whole run my first time, but I wish I could repeat that luck. I know I included the sRGB macro, which I don't need, and I know I ran it from the developer persona, and I know I accidentally created the affinity-format files too, and I was working on a sRGB workflow, but I've tried all the permutations of that my patience can handle, and I haven't been able to find that magic that makes me get the whole batch done with all 24 cores. Which means I'm stuck with one. Unless I can set processor affinity to 20.. maybe I can do that.. And in case you're wondering I regularly peg out all my cores (and GPU cores) on other things, so I don't have some hidden system instability. incidentally it would be nice if the batch settings (output dir/source dir/output type checkboxes/file type options) were persistent instead of resetting to default every time. And I'd love a ctrl-shortcut for batch or at least an alt-F-something shortcut. let me know if I can help debug. also a CLI for batch like darktable-cli would be super-amazing. I'd buy you a case of beer for that Oh how I miss having beers with friends...

Hello, Trying to load any image with Infer from LUT adjustment will crash the application. I’ve attached the crash log. Cheers! Photo iPad-2020-05-04-114905.ips

Hi, i had that issue once on publisher 1.7.1 but it disappeared after restarting my laptop. Now after updating to 1.7.2 win7, it occurs all the time. so here is my bug: i can write a word, but once i press "space" when writing text in a textfield or the "no-box"text , publisher crashes to the desktop. i can press space in a new textfield without problem, but when i enter text before it, the crash occurs. i tried solving the issue with reboot, and a full new start, no help. I thought it might be the size of my document, but the issue occurs in new documents as well. PC-details: Lenovo thinkpad p50 with 4k display, Win7 x64 -not yet- updatet aff. designer and aff. photo do not show that behaviour. crash-logs state this: Process Architecture: x64 Exception Code: 0xC0000005 Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap Information: Not Present please tell me, if you need more information on the issue, thanks in advance and for the otherwise very nice software solutions you provide! additional information: after updating (which came with an unsuspected restart) the program failed to start once correctly, but since then, besides the issue mentioned above, workes as usual

A document in Affinity Photo 1.8.3 where I found I need to modify text in Compound Group (silly me) was opened. Some consecutive individual characters were selected and deleted, the former text was further Compounded to two groups. Artistic text tool was selected, with current defaults and text was entered. While still in tool text was resized by shift-dragging from corner. Wasn't happy with what I got, did cmd-z and bang. Not sure if memory cleaner was still running, if not, then at least 1.5 GB, probably more, was free. Edit; was not cmd-z, but click to text size menu in top bar, at least did it now 😞 Hki-keskustelu-mainos-2020w20.afdesign ad-1-8-3-crash-2020-05-12.txt

Hi, I'm having trouble with Publisher repeatedly crashing. Using a newer iMac, Catalina. Everything worked fine for about 2 wks, then I started having difficulty getting the "Text" tool to work when I went back through to spot edit. It would activate the text frame but not allow me to edit the actual text. The cursor would be stuck center top of frame and the layer panel would jump to a different layer. My doc is a little long (160~ pages, barely any images yet). I thought the length might be an issue as I initially c/p as one long text block instead of dividing into chapters. Tried to c/p to create smaller chapter documents to later string together to start fresh, and now I get a repeated crash. It either happens when I click the text tool, or when I click on the new document to paste. If the text tool does not initially engage, it doesn't seem to happen. It's hard to pin down exactly which actions are causing it, but it's happening repeatedly, multiple documents. Thanks for any suggestions~ Crash report.rtf

Dear community, After working on my portfolio for 2 months–having it opened, saved & closed as many times–I encountered today my first bug regarding AP. AP crashes every time I try to open a specific file. I made a copy of the file on my desktop, and the copied file opened with the assets being missing. So, my guess is that It should be an assets (loading, indexing, etc) issue... I tried reinstalling AffPub, but it still doesn't open the specific file... I could try to re-link the "missing" assets of the file but is there a more optimal solution? I opened the copied file and tried to re-link the assets, following the advice read in various threads here, but it seems that I have to do it one by one... and that is no bueno! Needless to say, I tried to replace a random asset in my copied file (supposedly AP would automatically re-link all of the assets, as per discussed at another thread), but it didn't work either. Could you please make the process a bit easier? Re-linking a batch of images, instead of one by one, should this bug occur again? And–of course–could you check this issue with the file? I attached a pic of my report, if that is of any help! Semper Fi, Affinity! Thank you very much in advance, Chris

I too seem to have random crashes again when using a pen input as well, totally random but usually when trying to crop a picture, click and hold on the border cursor and hey presto Affinity is gone. It seems to happen after a certain amount of processing never straight away. I've attached the last couple of crash reports. 7f3660d3-2998-4056-be37-b080d575508f.dmp 757299f7-6c81-40c4-bd79-f17b52fcc458.dmp

Hi, Publisher crashes every time I hit the spacebar when in a text window. Thanks, Matt

Recently I have started painting in Designer. I use a Huion kamvas 16 pro. I have the software up on my main display and basically just the file up on my tablet. I use the tablet's pen on the tablet and configurate brushes and such with my mouse on the other display. Now I have experienced several (4) crashes, losing a lot of progress. These crashes don't work like regular windows crashes but rather make the program freeze in place but dont make it have that white overlay. The only option i have after that is force closing the program. At this point the program will ask if I want to save the file but I can't answer that because the pop-up is on screen for only a split second. Specs: B450M PRO-VDH MAX Motherboard RTX 2070 Super Graphics AMD Ryzen 5 3600 @3.6Ghz 16G Ram Win10 Pro running on an ssd Thanks