Jump to content
Brad Brighton

DATA LOSS in 1.7.0.128

Recommended Posts

In the process of attempting to repro this: 

 I discovered another scenario of the data loss I originally reported in this: 

Now, this time there's no crash but there IS still a (?) scenario where if startup is somehow short-circuited, the recovery/open file list appears to be lost.  I had 6 files open in the process of trying to quit soon enough to repro the crash and in one of the attempts, I managed to quit before any files were opened (visually) and the next time I opened the Photo beta app, it was as if there were no open files.

The files in question were in various states of completion (this is just a state description, not a "I'm using beta for production, how could you!?!") so there was actual data loss, not just the file list (which would be bad enough on its own).

The steps I was trying (timing varied slightly through the attempts):

  1. Make sure you have a "previous state" setup of open files (I have had a mix of afphoto and RAW reopens)
  2. Launch Photo beta (128)
  3. Attempt to quit at the various opportunities -- the ones I noticed:
    1. Before any window is open
    2. Once the main window is open but before the splash screen or any content tabs display
    3. After the splash but before content
    4. (normally) once content and splash both are displayed
  4. Relaunch Photo beta -- if you've triggered the situation, you'll see a blank slate instead of the expected reopened files.

I wasn't able to determine which of these scenarios cleared the recovery/state improperly.


https://bmb.photos Focus: The unexpected, the abstract, the extreme, including paper outputTools: macOS (Primary: Mojave, MBP2018), Canon (Primary: 5D3), iPhone (Primary: X), Epson

Share this post


Link to post
Share on other sites

Hey Brad Brighton,

I'm struggling on Mac. However I tried it on Windows and managed to get my app into a state where it wouldn't open after trying step 3.2 o.O 

Could you try this in the Release Candidate?

 

Share this post


Link to post
Share on other sites
1 hour ago, Chris B said:

Could you try this in the Release Candidate?

.134 (RC2) is out now (at about the same time you were posting, Chris :) )

 

 


-- Walt

Windows 10 Home, version 1903 (18362.145), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.1.404 and 1.7.1.404 Beta   / Affinity Designer 1.7.1.404 and 1.7.1.404 Beta  / Affinity Publisher 1.7.1.404

Share this post


Link to post
Share on other sites

@Chris B I've been away and still catching up on life. As soon as I can take the time, I'll re-check with whatever version seems to be current at the time (GM1?!?)


https://bmb.photos Focus: The unexpected, the abstract, the extreme, including paper outputTools: macOS (Primary: Mojave, MBP2018), Canon (Primary: 5D3), iPhone (Primary: X), Epson

Share this post


Link to post
Share on other sites
On 5/31/2019 at 10:09 AM, Andy Somerfield said:

I have some confidence that this got fixed in either RC2 or GM - if not, please let us know.

Thanks,

Andy.

Will definitely let you know. Thanks for chiming in, @Andy Somerfield


https://bmb.photos Focus: The unexpected, the abstract, the extreme, including paper outputTools: macOS (Primary: Mojave, MBP2018), Canon (Primary: 5D3), iPhone (Primary: X), Epson

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×