Slow in view mode, right? Not in browser mode..?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".
Viewer slow as hell
Moderators: helmut, XnTriq, xnview
Pierre.
Yes, when in the viewer.xnview wrote:Slow in view mode, right? Not in browser mode..?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".
Get the bugs fixed, THEN start adding features. It sucks, but someone has to do it.
Ok, currently the view has been optimized only in browser mode (fullscreen)Danny wrote:Yes, when in the viewer.xnview wrote:Slow in view mode, right? Not in browser mode..?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".
Pierre.
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 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!
Pierre.
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:
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.
Code: Select all
while (true)
a = 1+1
Could you send me your email by PM, i owuld like to send a test versionstax 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:
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.Code: Select all
while (true) a = 1+1
Pierre.