oops "unable to open result"

[Bruce Wayne]

After each benchmark run 3DMark tells me it cannot open my result. I'm convinced the reason is that my windows "documents" folder where 3DMark stores it's results is mounted to a network drive, but this should work. I can even see the result file in the correct folder, and I can even load it manually into 3DMark.

Please fix this!



PS: The log shows

java.nio.file.ReadOnlyFileSystemException: null
at com.sun.nio.zipfs.ZipFileSystem.checkWritable(ZipFileSystem.java:155) ~[zipfs.jar:1.8.0_91]
at com.sun.nio.zipfs.ZipFileSystem.newOutputStream(ZipFileSystem.java:496) ~[zipfs.jar:1.8.0_91]
at com.sun.nio.zipfs.ZipPath.newOutputStream(ZipPath.java:792) ~[zipfs.jar:1.8.0_91]
at com.sun.nio.zipfs.ZipFileSystemProvider.newOutputStream(ZipFileSystemProvider.java:285) ~[zipfs.jar:1.8.0_91]
at java.nio.file.Files.newOutputStream(Files.java:216) ~[na:1.8.0_91]
at com.futuremark.choros.util.BenchmarkRunUtil.addFileToZip(BenchmarkRunUtil.java:197) ~[choros.jar:na]
at com.futuremark.choros.util.BenchmarkRunUtil.stopBenchmarkLogging(BenchmarkRunUtil.java:180) ~[choros.jar:na]
at com.futuremark.choros.util.BenchmarkRunUtil.runBenchmark(BenchmarkRunUtil.java:133) ~[choros.jar:na]
at com.futuremark.choros.apis.BenchmarkRunApi.runTest(BenchmarkRunApi.java:135) ~[choros.jar:na]
at com.futuremark.choros.apis.BaseApi.handleRequest(BaseApi.java:132) ~[choros.jar:na]
at com.futuremark.choros.server.ChorosServer.lambda$onMessage$0(ChorosServer.java:246) ~[choros.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]

[UL_Jarnis]

This is caused by your Documents folder being in a location that says "permission denied".

Two common scenarios;

- Documents folder is on a network drive. Windows then thinks writing there is scary and should require special permissions and that breaks things.

- Documents folder is being synced to a cloud service (onedrive, dropbox etc.) and that temporarily locks the result file, causing benchmark to break due to being unable to write there.

We have a workaround in the works and hope to have it in the next update to 3DMark.

[Bruce Wayne]

Thanks for the answer, in my case it's definitely the reason that the documents folder is on a network drive.

Looking forward to the next update