Jump to content
You must now use your email address to sign in [click for more info] ×

Jeffjn

Members
  • Posts

    54
  • Joined

  • Last visited

Recent Profile Visitors

1,097 profile views
  1. It doesn't seem to have. The "Crossreference" feature appears to to be the same. It was the first thing I checked!
  2. FWIW, I had this issue, at least I assume it was the Net Framework issue, as my laptop had not installed that update and was fine, but my desktop had and would crash whenever I opened a large save file with what looked like a memeory leak. Instead of removing the Net Framework update, I noticed that the 22H2 feature update was pending. I let that install and the issue went away.
  3. EXACTLY THREE YEARS LATER 🙂 I appreciate the video showing the workround, but I really think Affinity should be implementing this feature properly by now.
  4. I'm posting again on this thread, but this time with good news - it looks like this has been fixed in 10.4. I've managed to merge the three parts of the latest update of my book. It's using 10gB of menory, but that's not growing as I sit here. 720 pages and at least 300 illustrations.... I'm going to trad carefully, but it's looking good.
  5. Having installed the 1.10 update with eager anticiption, bearing in mind it's claims to have done a great deal of work on Memory Management, I'm sad to report that this issue for me is still occuring. At this stage I'm trying to merge the section of the book so I can work with just one file, making indexing less painful as well as simplying the publishing process, but I'm seeing the same issues with silent crashes as soon as I approach the page/illustration counts that was causing me issues before. Is there anyone at Afinity who could take another look at this? I'm happy to work with them to provide examples and bug reports.
  6. I'm just bumping this after all this time to see if anyone bites. I've since had to just use merged PDFs to create my next book.
  7. ADDED - I've remembered one that is very easy to replicate. Load the large file I posted earlier, then save it with a different file name. Now close AP and restart it (to clear out any memory it is hanging on to). Open the first file. Wait for the CPU load to drop to be sure the task is completely finished. Leave the first document open open and open the copy you just created. After while open the task manager. It will be using about 15% CPU (in my case) or more on a slower machine. You can sit and watch that all day, the file never loads. If you want to close AP you have to use the task manager.
  8. Thanks for the reply Pauls. When this does get fixed, will you post back here please? I don't think its the only issue with large files, but the most obvious one to demonstrate.
  9. I'm going to have to bump this thead, sorry. Are you guys looking at this, or shall I produce another bug receipe? (believe me, it's not hard to do so )
  10. Thanks. I did google the subject, and downloaded one of the most likely looking (which didn't work with my files). Some of the google results offered a service (Upload your files and we will merge them, which is a good way to put something in the public domain). One site said that the least stress-free and safest way was to buy Acrobat, and as I was past my deadline I succumbed. However, if you have a recomendation I'd love to hear it, as I now have time to experiment and don't want to spend £180 a year! AP should be able to do this as one PDF, just like Page Plus, because I don't want to manually merge the indexes, which is the real pain.
  11. Hopefully this is still being investigated - it's happening in the latest beta as well. Can I reproduce some more of the bugs I've seen, or should I wait for this one to be investigated first? Thanks
  12. Thank you. I'll poke about a bit, but wait for their feedback before pestering you with more information 🙂
  13. Ah, Progress! I'm assuming that's the intial receipe, not the second one. I didn't realise (until just now) that Onedrive also monitored the Desktop and Documents folders when I previously tried eliminating it from my tests. However, I've briefly tried the following: Moved all my data files to a new folder on my C drive that isn't monitored by Onedrive. Told Onedrive to stop monioring Documents, Pictures and the Desktop Stopped Onedrive from starting up when Windows starts Rebooted the computer Tried the receipe with the files from the new isolated folder. Sadly, the same crash straight to the desktop is still occuring. I have to go out now, but would there be anything else I don't know about using Onedrive that might be relevant? Does Publisher put files somewhere that might still be monitored?
×
×
  • 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.