Project Not Loading

[Erica176]

I am working on a digital planner and the file is large, over 136k KB.  I'm not sure why it's so large as the planner I made previously was only 4k KB and had more pages.  Possibly it's due to the images I've included.  Regardless, my computer has plenty of memory and storage so it shouldn't be an issue.  However I've been trying to load my document for over a day and it's not loading.  I'm not getting an error message, it's just sitting there saying 'loading'.  Is there a fix for this?  I will be very upset if I have to start from scratch.  Also, if this is going to be a normal occurrence, I won't be able to use this software any longer as it's wasting way too much of my time.  And that's too bad because I love this program and find it extremely user friendly.  Any assistance would be greatly appreciated.

[carl123]

Can you upload the document to the forum?

[Erica176]

Yep, here it is.  I'm also uninstalling and reinstalling affinity 2 in the hopes that will help.  

Red Leather Planner.afpub

[carl123]

Thanks

I've been trying to open it for 30mins and it's not opening so something it wrong

I think the official support staff will need to take a look at it, once they get to this thread

[Old Bruce]

I have the same experience as @carl123 so then I did a hex dump of the file (with BBEdit) and there are massive parts where there are hundreds of lines of zeros. This means there are areas where there is no information.

[Erica176]

Thank you both for looking at it.

@OldBruce that's strange it would do that.  I didn't do anything different, I wonder if there's an issue while I'm saving it.  I did notice when I would save changes that the KB would fluctuate anywhere from over 150k to 90k.  No clue what's going on with it and sadly I just don't have time to keep messing with it.  I'll have to create my new project in another system that doesn't have these issues.

Again, thanks for the help!

[4dimage]

I couldn't open your file either. I have more than 32 GB RAM free for Publisher so this would not be a problem.

 

--- I)

1) Started Publisher fresh for every test cycle.

2) With publisher running i open your file

3) Open dialog shows up. The file loads - slowly but the status bar goes just up to 100% after some 20 seconds.

4) Nothing happens - waited for about 2 minutes.

 

From the taskmanager: during the first period while statusbar changes the RAM usage increases constantly, there is some moderat CPU action (8 core -> max. 10% overall).

After the status bar reached 100% there is no more change in RAM usage (about 6 GB) but there is constant CPU action (about 7%). These values continue for minutes. Nothing else happens in Publisher.

I tried this with hardware acceleration on and off. No significant difference.

 

--- II)

After some time (max. waited for 2 minutes) i quit the load dialog ("Abbrechen") and the dialog closes and everything seems to be ok. The app is still interactive. I even can create new documents via menu, work on them, save and close them. Everything still works as usual with other documents.

But the task manager still shows high RAM usage (6 GB) although the Open process seems to be interrupted by me (the user) and i think have closed all documents now. There is still something going on in the background.

And as soon as i try to completely quit Publisher (Menu OR window-X or ALT+F4) i get the following warning:

 

Can't quit Publisher the normal way no matter how often i try. So have to force shutdown via taskmanager.

Can reproduce the above behaviour as often as i want.

Don't hav a crash report in ..\.affinity\Publisher\2.0\crashreports\reports.

 

 

[Erica176]

So I've been playing around with this again mainly because Affinity is the best program to create digital planners.  I tried others and they just aren't doing it for me.  And I believe I've found that if I 'Save As' each time I save instead of just 'Save', it's not creating all that extra fluff that was bogging it down and inflating the file.  Sadly I had to start from scratch but hopefully it will continue to work for me.  

Thank you all for checking this out though.  

[NathanC]

Hi @Erica176,

I've logged your broken file with the developers so they can diagnose what might have caused the file to corrupt.