Page 1 of 1

1.9.2: Large file size displayed incorrectly in status bar

Posted: Tue Jul 29, 2025 7:46 pm
by Mapaler
Issue 1
XnView: MP 1.9.2 - 64 bit

OS: Microsoft Windows [Version 10.0.19045.6159] - 64 bit

When opening a file with an extremely large size, the file size displayed in the status bar is incorrect.

Effect: Digital display error.

To reproduce:
  1. Download eso1242a.psb 24.6 GB (26,455,654,863 Byte) at https://www.eso.org/public/images/eso1242a/
  2. Open eso1242a.psb by XnViewMP.
  3. Observe the file size displayed in the status bar.
Actual behaviour (bug): The status bar shows an incorrect or incomplete file size 654.77 MB. :bug:

Expected behaviour: The status bar should display the correct file size 24.6 GB.

Issue 2

When opening a specific file, the default anti-aliasing feature causes significant lag during operations like fitting the image to window size. Even minor adjustments to the window size result in the program becoming unresponsive.

Suggestion:

Automatically disable anti-aliasing for files exceeding a certain pixel threshold to improve responsiveness.
Implement a pre-rendered intermediate-sized cache (or downscaled preview) for smoother interactions with large files.

This would enhance the user experience by reducing delays during window resizing or zooming operations for high-resolution files.
xnviewmp_aj5suyxgwk.png
xnviewmp_aj5suyxgwk.png (410.04 KiB) Viewed 62 times

Re: 1.9.2: Large file size displayed incorrectly in status bar

Posted: Wed Jul 30, 2025 5:53 am
by user0
Mapaler wrote: Tue Jul 29, 2025 7:46 pm Automatically disable anti-aliasing for files exceeding a certain pixel threshold to improve responsiveness.
such things should be implemented via modal popups, not via automatic "magic behaviour"
(if bother at all, as opening huge files is not a common task and user should be aware of what he is doing in the first place)

Re: 1.9.2: Large file size displayed incorrectly in status bar

Posted: Thu Jul 31, 2025 1:34 pm
by xnview
Mapaler wrote: Tue Jul 29, 2025 7:46 pm Issue 1
:bugconfirmed: Thanks to your detailed description I can reproduce the problem.