Viewer slow as hell

Post by **xnview** » Fri Jun 29, 2007 6:34 am

Danny wrote:Another thing just occured to me. In comparison to "that other program" switching from one image to the next is also slow. It takes distinctly longer than one second two skip through images (again, 4MB JPGs), while skipping happens almost immediately in "that other program".

Slow in view mode, right? Not in browser mode..?

Danny · Post by **Danny** » Fri Jun 29, 2007 2:50 pm

xnview wrote:
Danny wrote:Another thing just occured to me. In comparison to "that other program" switching from one image to the next is also slow. It takes distinctly longer than one second two skip through images (again, 4MB JPGs), while skipping happens almost immediately in "that other program".
Slow in view mode, right? Not in browser mode..?

Yes, when in the viewer.

Post by **xnview** » Fri Jun 29, 2007 3:16 pm

Danny wrote:
xnview wrote:
Danny wrote:Another thing just occured to me. In comparison to "that other program" switching from one image to the next is also slow. It takes distinctly longer than one second two skip through images (again, 4MB JPGs), while skipping happens almost immediately in "that other program".
Slow in view mode, right? Not in browser mode..?
Yes, when in the viewer.

Ok, currently the view has been optimized only in browser mode (fullscreen)

stax · Post by **stax** » Sat Aug 11, 2007 8:44 am

There is some kind of threading or message pumping bug. The viewer is slow as hell switching to next image in fullscreen mode while performing video encoding with another application (thread priority low). The bug occurs only when viewer fullscreen is entered directly from the browser (View in fullscreen (F11)). It doesn't occur entering from normal viewer mode!

Post by **xnview** » Mon Aug 13, 2007 7:53 am

stax wrote:There is some kind of threading or message pumping bug. The viewer is slow as hell switching to next image in fullscreen mode while performing video encoding with another application (thread priority low). The bug occurs only when viewer fullscreen is entered directly from the browser (View in fullscreen (F11)). It doesn't occur entering from normal viewer mode!

Strange, this thread is created with a normal priority...

stax · Post by **stax** » Mon Aug 13, 2007 8:35 am

Can you reproduce it? It happens when CPU load is 100%. A easy way to get this is using a WSH JScript, create a text file with extension js with code:

Code: Select all

while (true)
    a = 1+1

use the task manager to set the priority to low and to kill the process, the host process is called wscript.exe or cscript.exe. Maybe you know a easier way to get full CPU load.

Post by **xnview** » Mon Aug 13, 2007 8:56 am

stax wrote:Can you reproduce it? It happens when CPU load is 100%. A easy way to get this is using a WSH JScript, create a text file with extension js with code:
Code: Select all
while (true)
    a = 1+1
use the task manager to set the priority to low and to kill the process, the host process is called wscript.exe or cscript.exe. Maybe you know a easier way to get full CPU load.

Could you send me your email by PM, i owuld like to send a test version