Saving Database Slow
I open ON1 2019 fiddle with one or more files, export one and close the program. The main program screen closes, but I get a popup saying that a database is being closed. That popup in my case is on screen for two minutes and all of the RAM attached by the application is still attached. What data base is being saved and why? Why does it take so long? Why is it still attaching the same amount of RAM as the entire application? And lastly is their anything I can do to improve or even stop this?
TIA,
Duncan
-
The database is where all of your work is saved. I don't know what it's doing or why, but I see the exact same thing.
1 -
The pop-up is "normal"; length of time was greatly reduced when I stopped using the catalogue function and started using albums.
1 -
Thank you Peter. Had to drop back to American spelling of catalog :) to find it. Still begs the question why would it take so long when only two files were changed.
0 -
My guess is PR catalog is constantly updating. Try removing folders from catalog just to prove this to yourself.
0 -
Deleted all the folders. Still pops up 'closing database', still hogs RAM while doing this but is faster at just over a minute. If I don't get any further reading the manual, I'll open a ticket.
0 -
Hi Folks, good to see familiar names here.
After 2018.2 I couldn't use catalogued folders, it just crashed every time. 2019 does allow me to use catalogued folders, but, boy does it take its time! And shutting down the database, at first I thought it had frozen, so I did a Force Quit (on Mac). I later discovered this was a bad idea as some on the on1 sidecar files disappeared, or maybe were never written before I Force Closed.
I now realise that it may simply be my aged iMac, because if I leave it, it does sort itself out, eventually.0 -
I have about 6000 images and on an 8 core 8000M/Bs CPU and 16GB of RAM (Windows 10) the Databse takes approximately 4 mins to shut down. All these images re in 1 catalogued folder (many sub) My Pictures.
Frequently, enterering the Browse module causes internimable delays. This is becoming very frustrating indeed. Does removing catalogues help?
0 -
Any solution or update to this issue? I'm experience same on - "Closing the database" dialog takes about 5-6 minutes on my Win10 PC.
0 -
I have found the issue I had with 2019.2 has now gone away with 2019.5
0
Please sign in to leave a comment.
Comments
9 comments