Jump to content

Recommended Posts

Posted

I don't have the steps for this yet, but I've been doing real work with the beta since it came out and it's frequently asking if I want to open a recovery version. It hasn't been crashing so the recovery versions should have been deleted.

My thought is the recovery version isn't always deleted when I closed a document that has unsaved changes, but when I try to test it I can't reproduce it. I'm mentioning this now in case anybody else has seen something similar.

This didn't happen with 2.4.

Posted

The issue can happen with an unsaved document. Sometimes (always while working on a real document), I'll create a second document for a test and draw a few objects. At some point I'll close that second document without saving it. I'll later quit Publisher beta, and when I next start it, I'm prompted to recover a document. I'm clicking yes each time now to see which document it is and the latest one was a test document with a single text frame in it.

If I look in my beta autosave folder, I see five files from March 16, 2023 to April 19, 2024 but none dated today. I deleted these just now - hopefully that's okay - but please let me know if I need to clear some data on startup.

Posted

There does seem to be a problem with Publisher 2 beta 2.5.0 not clearing the unsaved documents from the autosave. Like MikeTo I cannot definitely point to a recipe. But I see it happening a lot. I don't see this with Designer or Photo.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Posted
9 minutes ago, Old Bruce said:

But I see it happening a lot.

I have not noticed it yet, on Windows. I have not looked at it on macOS.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

  • Staff
Posted

I've seen this once too @MikeTO, but like yourself haven't had any luck in finding a recipe/reproducing it. Sometimes if you close the app down and it crashes on close it can cause the prompt to appear on next runup when opening the file that was open, but when I saw it I was fairly certain it wasn't after an app close.

Certainly one to keep an eye on, I'll dig around and see if I can find a way to reproduce it

Serif Europe Ltd. - www.serif.com

Posted

I'm working with the autosave folder open so I can keep an eye on it.

I left Publisher running with saved and unsaved docs open last night. I created a test doc this morning and then checked the folder - there were three autosave files, two saved last night, one this morning. I closed all the docs and quit Publisher - the files were not deleted. I restarted Publisher and was prompted to recover two documents. One was a test doc from last night that had never been saved, and the other was the unsaved test doc from this morning. I recovered both, closed them, and quit Publisher. The autosave folder still had one file in it. Restarting Publisher still didn't prompt me to recover that file. I tried making another new unsaved test doc with some linked images in case that is the trigger but I could get it to create another autosave file that it didn't delete. But that first one persisted so I eventually deleted it. I'll keep an eye on it.

Posted

Note that (by design) you are only prompted (when starting the application) for files that were active but have never been saved as an Affinity file. If you were working on a named file (e.g., abc.afphoto) then you will only be prompted for that one when you explicitly try to Open abc.afphoto, not when you restart the application.

Edit: This can be confusing if you're looking at the Autosave folder, as you cannot tell which .autosave files are for unnamed/unsaved files (which will prompt) and which are for named/saved files (which won't prompt).

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
1 minute ago, walt.farrell said:

Note that (by design) you are only prompted (when starting the application) for files that were active but have never been saved as an Affinity file. If you were working on a named file (e.g., abc.afphoto) then you will only be prompted for that one when you explicitly try to Open abc.afphoto, not when you restart the application.

I closed those files without saving them so the recovery version should be deleted.

In the past I've only ever seen recovery prompts after a crash when a document wasn't saved, but with the 2.5 beta I'm seeing recovery prompts regularly for documents that were closed before I quit Publisher. I'm not experiencing any crashes. The problem is due to the recovery versions not being deleted when the documents are closed but I can't find a pattern. Sometimes they're deleted, sometimes they're not. It's odd.

Posted

@MikeTO, one way this can happen is logged here, though I appreciate this isn't what is happening for you...

I'm seeing the same issue randomly when closing files without saving them irrespective of this method and likewise still have yet to find a repeatable step-by-step process.

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

I've also seen this. Just checked the APub-beta autosave folder and, indeed, it does have a file in it! And I know for certain that I closed a test doc without saving before quitting last time. In hindsight, it has does the same with that test doc more than once. I have kept closing it without saving before quitting, but it still asks to open recovery at next start. 

--------------------

New: 2023 Mac Studio M2 MAX 12-Core CPU/38-Core GPU 64GB Memory • 5k Studio Display • Sonoma
Prev: 2020 iMac 27 i7 (5k Rez), 72GB, AMD Radeon Pro 5700XT 16GB • Sonoma
MacBook Pro, 13", M1 2020 • 16 GB • macOS Sonoma
iPad Air 2022

Posted

@Jon P I have been having multiple crashes the last few days with Designer Beta 2.5 — especially with attempts to save a document. I had been trying to see what I could get away with, mixing Assets and Styles while using the Flood Fill Tool.  Sometimes Designer crashes in the middle of an action.  Other times it waits until I try to save.  Each time, when I click on Save, Designer crashes.  No window appears regarding recovery.  When I click on FILE>Open Recent and select the file that crashed, the Recovery file window opens.  When I click on that, the file opens to the original without any of the changes I had made and tried to save.  I have repeated this several times.

I have made a short video of this, in case anybody is interested.  I have several crash reports as well.


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted
On 4/24/2024 at 2:23 PM, jmwellborn said:

@Jon P I have been having multiple crashes the last few days with Designer Beta 2.5 — especially with attempts to save a document. I had been trying to see what I could get away with, mixing Assets and Styles while using the Flood Fill Tool.  Sometimes Designer crashes in the middle of an action.  Other times it waits until I try to save.  Each time, when I click on Save, Designer crashes.  No window appears regarding recovery.  When I click on FILE>Open Recent and select the file that crashed, the Recovery file window opens.  When I click on that, the file opens to the original without any of the changes I had made and tried to save.  I have repeated this several times.

I have made a short video of this, in case anybody is interested.  I have several crash reports as well.

You should probably create a separate thread for this, I'm not experiencing any crashes so I don't think it's related to the recovery file prompt.

Posted

Update on this issue - whenever it happens, not only is the autosave recovery file still present, but the hidden lock file wasn't deleted either.

This issue happens all the time, I'm getting it a dozen times each day with the beta.

Posted

@MikeTO  Are you getting the crashes also using Assets and Styles?  And do you still think I should create a separate thread?  I hesitate, because there seems to be a thread regarding Styles and Publisher and crashes. Don't want to be guilty of duplicating someone else's issue.

Video is attached.  Crash reports are available.  Please excuse the garish and vile colors.  I was purposely using sky overlays and styles with the Flood Fill Tool to see what I could get away with.  Apparently not much!

 

 

 

 


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted

I’m seeing the issue regardless of having previously saved the file then making edits and closing the file without saving changes. It happens with completely new unsaved files where no lock file has been generated where either closing the file using Cmd W or when quitting the app the autosave file simply isn’t removed…

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • Staff
Posted
On 4/24/2024 at 7:23 PM, jmwellborn said:

I have been having multiple crashes the last few days with Designer Beta 2.5 — especially with attempts to save a document. I had been trying to see what I could get away with, mixing Assets and Styles while using the Flood Fill Tool.  Sometimes Designer crashes in the middle of an action.  Other times it waits until I try to save.  Each time, when I click on Save, Designer crashes.  No window appears regarding recovery.  When I click on FILE>Open Recent and select the file that crashed, the Recovery file window opens.  When I click on that, the file opens to the original without any of the changes I had made and tried to save.  I have repeated this several times.

I believe this is likely to be the crash when saving after changing styles that is already logged with us, sometimes it may "randomly" crash because it auto saves and that triggers it, other times the manual save you are doing is triggering it.

I'll link this thread to that report too, incase you still see these crashes when it's fixed.

Quote

Update on this issue - whenever it happens, not only is the autosave recovery file still present, but the hidden lock file wasn't deleted either.

This issue happens all the time, I'm getting it a dozen times each day with the beta.

To clarify, this is after generally after shutting the app down? Or during the same app session, open/saving/closing/re-opening a file is still giving the recovery prompt? If it's after closing the app down, I suspect it's potentially crashing on close, so not removing the lock file (which should time out after 5 minutes or can be manually deleted), and leaving a recovery file which is picked up on next file open.

Serif Europe Ltd. - www.serif.com

Posted
5 hours ago, Jon P said:

To clarify, this is after generally after shutting the app down? Or during the same app session, open/saving/closing/re-opening a file is still giving the recovery prompt? If it's after closing the app down, I suspect it's potentially crashing on close, so not removing the lock file (which should time out after 5 minutes or can be manually deleted), and leaving a recovery file which is picked up on next file open.

Yes, it's always after quitting and restarting the app. I'm not seeing any crash reports in the folder. Also, the lock files are often days old by the time I notice them, so well over 5 minutes.

Posted

Just to confirm for me it’s the autosave files that are sometimes not deleted rather than the lock file. 

It’s the autosave file not being deleted that is causing the issue when reopening the app. Sometimes the autosave file is deleted sometimes it’s not.

As @MikeTO, the apps are not crashing, this happens simply after a Cmd Q then reopening the app.

If I drag the non deleted autosave file directly into the app so the file opens then quit the app the autosave file is usually (but not always) deleted and the file will reopen without the ‘Open Recovery?’ message popping up as expected…

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • Staff
Posted

Thanks, I'll continue to poke and see if I can find a recipe that would cause the autosave files/lock files to not be removed when closing the file. I've still only seen this the once so far however.

Quote

Also, the lock files are often days old by the time I notice them, so well over 5 minutes.

This figures, as if it's not been removed when the file was closed it wouldn't then get cleaned up. If however it's not been refreshed and the lock file is more than 5 minutes old it won't be treated as an active lock file and prevent the file from being opened again, so opening and closing it should then remove the lock file (unless for some reason like what is being investigated, it isn't cleaned up on close)

Serif Europe Ltd. - www.serif.com

Posted
40 minutes ago, Jon P said:

I'll continue to poke and see if I can find a recipe that would cause the autosave files/lock files to not be removed when closing the file. I've still only seen this the once so far however.

Like @MikeTO, I’m seeing this constantly but have stilled failed to find a 100% step by step to replicate it…

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

A major correction to this report. You don't have to quit the app for this to happen or close a document with unsaved changes. You can work on a document, save it, close it, and the autosave file won't necessarily be deleted. Re-opening will give you the recovery prompt.

This has been happening to me so many times that I haven't been paying strict attention, but I noticed this yesterday and it happened twice this way today. So it can't be due to a quite crash when closing the app.

  • Staff
Posted

So I think this will end up being related to this thread and the issue logged from it. I can reproduce that issue even after changing DPI and saving, so it could be some other commands are triggering it. I've raised this in that issue, and will link this thread to it, so will be curious when we get a beta with a fix in for that issue if you continue to see this behavior

Serif Europe Ltd. - www.serif.com

  • Staff
Posted

An issue raised in this thread ("[Mac] Changing DPI and closing the file without saving changes shows 'Open recovery file?' when reopened") has now been reported to the developers by the testing team (Ref: AF-2894). Thank you very much for reporting this issue to us.

Posted

One more point - it can happen even with an unmodified document. For another test I was doing, I opened two documents, selected and copied text from the frames in both documents and pasted that into frames in two new documents I created, and then closed both original documents. Re-opening the documents gave me recovery prompts. I'm unsure of the exact order and I couldn't reproduce it when I tried to do the same thing so there's something strange going on.

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.