Another Issue... this one a little more serious.


Hello there…
So I have been using FRV for about a week now and have been pretty happy with it. But just recently I was accessing some images on a shared volume of a Mac Mini (running Snow Leopard) from a MacBook Pro (running High Sierra). I was in a folder of nef files and had rejected a few, and then moved to some other images using the arrow keys when it went unresponsive.
After a couple of minutes I finally force quit FRV, and afterwards received an alert window saying the network drive I was browsing was no longer connected. I have a sneaking suspicion FRV took down my server as I was no longer able to connect to it via afp or vnc until restarting it.
I suppose it is always possible the server went down and forced FRV to go unresponsive, but it is a rock solid 24/7 device so that is highly unlikely. A copy of the log is below… perhaps you can let me know what caused this.

Dear Sir:

FastRawViewer uses operating system services to access network (or any other) volumes, it uses only standard file access and nothing more.

The thing that may differ from other programs is network/disk load: FastRawViewer may read many files in parallel, resulting in higher (than usual) load.

You may try to reduce FRV 'parallel load' using settings for single HDD drive:


Alex Tutubalin/FastRawViewer team

Thanks. So the log doesn't tell you anything more specific?

This is stack trace for the program waiting for file information from afp volume.


Alex Tutubalin/FastRawViewer team

Add new comment