Windows 10, but it might be applicable to Apple. About 5 days ago my 2019 ON1 took a nose dive. Up until that time, it was usable. I have a powerful computer with lots of memory and a top end Nvidia GeForce GTX 1080 with 8GB of memory. All of my working drives are either NVMe or SSDs. No spinners.
When I was in Browse, and in a subdirectory that had lots of images, if I scrolled down thru the thumbnails, at some point during the scrolling, my machine would lock up for up to 7 minutes. No mouse, no clock update, no nothing. Sometimes even my screens would go black like the computer rebooted. But it did not reboot. If I waited long enough, the machine would clear it's bottleneck. But then all I had to do was scroll down or up in a catalog folder and it would do it again! In the same catalog directory no less! WTH ???
I had no issues running 2018.5 on any of these catalog directories. I tried Process Lasso, and a smaller version called CPUBalance. I tried lowering ON1's process priority to Low. I took away 10 (of the 12) processors from ON1. I tweaked the GPU via the NVidia control panel. I deleted the scratch and cache under ON1 program settings. Nothing made any difference. I have almost 40 years of Windows programming under my belt and Linux too. This was mind blowing. Then all of a sudden I happened to notice that the System OP drive (which is a screaming e.vme) was being bombarded with I/O. Or at least that was a view in Task Manager that I noticed right after the lockdown freed itself. Then it dawned on me... The browse catalog itself is doing something very, very bad.
From an old bug ticket I submitted, I knew the catalog was stored in the following directory. I also knew that ON1 would create a new directory if it was not there.
C:\Users\username\AppData\Roaming\ON1\ON1 Photo RAW 2019/ExploreService
So I went and renamed that ExploreService directory to something else and when ON1 started up, it said I had no catalog. And when I went to the drive folders that corresponded to the catalog folders that were causing my machine to go into lockdown for 6 or 7 minutes at a time, it did NOT have any lockdown. I could scroll up and down to my hearts desire. Woohoo!!!!
So I added the hard drive directories back into the empty catalog. I gave ON1 an hour or so to get smart about the catalog. Then I went back into the catalog and I had the same lockdown issues as before while scrolling down thru thumbnails. Sad, but at least the problem is repeatable.
I then went into the Local Drive area that has the original folders that I just put into the catalog. And when I scrolled up and down in the Local Drive area (Not the catalog), it STILL froze and did a lockdown. Minutes went by, mouse movement stopped.
So I went back to an empty catalog. Now I am accessing my images via the Local Drive section and I am able to do all of my edits, scrolling, etc without any system freezing or lockdowns.
Bottom line: There is something very seriously wrong with the catalogs and how they are used in ON1 2019. If you can do without catalogs for the time being, you may want to try renaming your catalog folder and working in the Local Drive area and see if you are getting better results. I am not going to submit this as a ticket because I have no idea how they expect me to send that amount of data to them. I just hope that enough of the existing browse issues point to this problem and they will get a patch out soon.
It could very well be a GPU issue as I have no way to telling if the computer is still functioning and only the displays are locked down. But I have two monitors both are frozen as well as the mouse. I am using the latest NVidia driver on my GeForce GTX 1080 with 8GB of ram.
Please sign in to leave a comment.