起動遅延トラブル(English: 'Image loading is slow')

[Xanardi]

ローカルディスク(NTFS)上の画像を表示する場合，画像のフルパス上にシンボリックリンクが含まれていると，QuickViewer起動後，画像表示まで長い時間を待たされます。
実行環境はWindows10です。

• X:\foo\bar\pictures\target.jpeg // 表示に差し支えない
• X:\foo\[pictures-simlink]\target.jpeg // このパスをパラメータで表示しようとすると遅い

[kanryu]

I found out that you are inquiring about the following:

(Translate from Japanese to English)
When displaying an image on a local disk (NTFS), if a symbolic link is included on the full path of the image, it will take a long time to display the image after starting QuickViewer.
The execution environment is Windows 10.

• X:\foo\bar\pictures\target.jpeg // There is no problem with the display time
• X:\foo[pictures-simlink]\target.jpeg // It takes time to display the image of this path

@Xanardi First of all, QuickViewer is developed in English, so ask questions in English as much as possible. Many people other than you read your issue.

As for your inquiry, when I tried the same on my PC, the problem did not reappear (both SSD and HDD).
QuickViewer does nothing special to read images and archive files other than an aggressive memory cache, and accesses each file in the usual way.
This issue is probably not a bug on the QuickViewer side, but on your PC side.
Not all files on SSD or HDD storage can be read at the same speed (read speed, latency). It may also take seconds if the condition is bad.

There are many possible causes, such as bad sectors or fragments in the storage, problems with NTFS integrity, and frequent errors in bus signals such as SATA.

[Xanardi]

EN (Translation from JP)
I couldn't confirm the symptoms, so I tested it a little more.
It seems that the shader selection is also included in the condition.

• Bicubic interpolation, Lanczos 3 & 4
  • Slow (30 sec over)
• Bilinear interpolation, Nearest-neighbor interpolation
  • Not reproduced

JP (Native)
症状が確認できないとのことで，もう少しテストしてみました。
シェーダーの選択も条件に含まれるようです。

• バイキュービック補間, Lanczos 3 & 4
  • 低速 (30秒以上掛かる)
• バイリニア補間, 最近傍補間
  • 再現せず

[kanryu]

@Xanardi By the way, is your QuickViewer a 32-bit version? For QuickViewer, the 32-bit environment is very prone to memory shortage, and image loading may be delayed randomly due to frequent memory allocation failures.

[Xanardi]

EN (Translation from JP)
Just in case, I tried to output the hash value with sha256.
It was a 64-bit build.
As far as the task manager is concerned, the memory of the PC is about 20GB / 32GB free.

JP (Native)
念の為sha256でハッシュ値を出してみました。
64bitビルドのものでした。
タスクマネージャーを見る限りでは，PCのメモリは 20GB / 32GB ほどが空いています。

sha256
5a6538e7328f833c1a483df1472111085b8a6fe33a9745ca49e8e2a97ab60dbc *QuickViewer.exe

[kanryu]

I understand that it is not a 32-bit version. However, your report is not reproducible at this time and will not be resolved. If you really need to fix it, please fix the source code and make a pull request.