Qt team has replied "It is normal on Windows due to the fact it loads the dependent Qt dlls at start up and this can also cause other dlls to be loaded."
Do you have same delay for first startup with other Qt based app like 'db browser sqlite'?
xnview wrote: ↑Mon Nov 15, 2021 12:17 pm
Qt team has replied "It is normal on Windows due to the fact it loads the dependent Qt dlls at start up and this can also cause other dlls to be loaded."
Do you have same delay for first startup with other Qt based app like 'db browser sqlite'?
I don't know what app used qt
But tested with this testapp (I'll call it this since) and DB Browser for SQLite @XnTriq provided
xnview wrote: ↑Tue Mar 09, 2021 10:10 am
could you try to put this file in XnView MP folder, and start it?
First cold start time after a windows cold restart (rebooted 3 times, run one target a time)
testapp (application.exe): ~1.5s
DB Browser for SQLite.exe: ~6s
XnViewMP.exe: ~9s
Last edited by BK201 on Mon Nov 15, 2021 12:49 pm, edited 4 times in total.
Same slow as xnview, first run takes 16 seconds, second and later runs takes 1 seconds to startup
spec:
You mean post things like this?
Yeah I got a better pc so it's faster...a little bit
btw this debug screen was generated by the in-app feedback button by screentogif
1.png
You do not have the required permissions to view the files attached to this post.
Brian wrote:Most likely it is trying to access a network resource and can't find it. Usually because the server it's on isn't responding or no longer exists. Timing it more accurately can help troubleshooting as the delay will always be over the timeout value.
Try and see what it is trying to open or access. I would suggesting using Sysinternals Process Monitor and/or Process Explorer.
A 15 second delay is often from trying to access an IP address that doesn't respond but should be reachable. You can use Sysinternals TCPView to see what address it's trying to access (open a connection to).
Brian wrote:Most likely it is trying to access a network resource and can't find it. Usually because the server it's on isn't responding or no longer exists. Timing it more accurately can help troubleshooting as the delay will always be over the timeout value.
Try and see what it is trying to open or access. I would suggesting using Sysinternals Process Monitor and/or Process Explorer.
A 15 second delay is often from trying to access an IP address that doesn't respond but should be reachable. You can use Sysinternals TCPView to see what address it's trying to access (open a connection to).
Thanks for the tool
TCPView didn't show any connection from xnview
promon shows that xnview takes tons of time loading some dlls
pmon.png
Here's the full log (this run takes 8 seconds btw):
You do not have the required permissions to view the files attached to this post.
BK201 wrote: ↑Tue Nov 16, 2021 9:28 amTCPView didn't show any connection from xnview
promon shows that xnview takes tons of time loading some dlls
Thank you for your patience and continued support, BK201
BK201 wrote: ↑Tue Nov 16, 2021 9:40 amI didn't found xnconvert.exe in xnviewmp folder
XnConvert is a separate application which consists of XnView's batch processing engine (no view and no browse mode etc.). XnConvert is also based on Qt, but comes with less DLLs. v1.94.0 is the latest release.
BK201 wrote: ↑Tue Nov 16, 2021 9:28 amTCPView didn't show any connection from xnview
promon shows that xnview takes tons of time loading some dlls
Thank you for your patience and continued support, BK201
BK201 wrote: ↑Tue Nov 16, 2021 9:40 amI didn't found xnconvert.exe in xnviewmp folder
XnConvert is a separate application which consists of XnView's batch processing engine (no view and no browse mode etc.). XnConvert is also based on Qt, but comes with less DLLs. v1.94.0 is the latest release.
7 seconds
pmon - xnconvert.png
You do not have the required permissions to view the files attached to this post.