|
|
Post by Tony Ei7bmb on Mar 28, 2022 10:57:12 GMT
Hi Guys, when on click on the shortcut for JTDX 159 sometimes it does not start. It appears in Task manager and the CPU usage goes way up. If click on "end task" (sometimes I have to do this twice) I can then get it to run. Any ideas where I should look to try diagnose the problem? I am running windows 10 with a fast AMD CPU.
Thanks for reading
|
|
|
|
Post by Wolfgang OE1MWW on Mar 29, 2022 9:32:31 GMT
Tony,
you are not the only one, seeing this. Did happen on releases before 159 too.
My guess, it is related to the QT library, that supports the GUI of JTDX.
Could be, other software is using the QT5 libraries too and conflicting.
If you search 'QT*.dll' with a tool (Everything from http://www.voidtools.com)
you may see a lot of those DLL in your PC. The only solution I found, either
to restart the PC or the way you describe it. Up until today, there was no
hint what exactly causes that known bug.
73's de OE1MWW
Wolfgang
|
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 12:37:49 GMT
Vielen dank Wolfgang. I'll do a search for QT DLL and see what shows up.
|
|
|
|
Post by w9mdb on Mar 29, 2022 13:04:19 GMT
I can recommend installing ProcessHacker -- you can then click on the properties on JTDX and look at the Modules tab to see all the DLLs referenced. The tooltip for each DLL then shows you the path. processhacker.sourceforge.io/ |
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 13:23:21 GMT
Thanks for the info, I have installed process hacker, quite a few DLL's under modules tab. I'll check again next time JTDX does not start
Edit: Ok when JTDX does not start and I take a look at modules tab in process hacker I get this message "Unable to query module information dues to process conflicts. Screenshot below which is clickable
|
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 14:49:56 GMT
Tried this again and QT5Widgets.dll is showing in orange, then then all listings turn to red and then list goes blank with message above. Am I right in thinking QT5Widgets.dll is the problem ?
|
|
|
|
Post by w9mdb on Mar 29, 2022 14:50:29 GMT
Unfortunately it didn't get far enough to keep the DLLs loaded.
PowerShell can get a list of all the dlls loaded like this for example.
Get-Process | Select -Expand Modules | Out-File -FilePath \temp\dlls.txt
Then you can load dlls.txt and look for Qt
|
|
|
|
Post by w9mdb on Mar 29, 2022 14:56:24 GMT
Not necessarily QT5Widgets
|
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 15:28:04 GMT
Thanks for the help. I notice that when I look in Task manager when JTDX does not start correctly that jtdxjt9.exe is not running.
|
|
|
|
Post by w9mdb on Mar 29, 2022 15:42:30 GMT
It never gets far enough to run it apparently.
|
|
|
|
Post by w9mdb on Mar 29, 2022 15:43:45 GMT
debug build MS Windows, 64bit cloud.mail.ru/public/mDdS/HNhVJWZRZchecksum jtdx-2.2.160-rc1-debug-win64.exe SHA-256: 0C0839BFD0C8085A6D52550A74EB95FAF86B31EF95CB4B8886E18B8C7854C443 Debug build is dedicated to trace down possible Hamlib and TCI bugs, this build can be installed in case any related issue being observed. Two logs will be recorded: in %TEMP% directory, file name is JTDX_trace.log in JTDX QSO log directory, file name is jtdx_debug.txt |
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 16:09:38 GMT
Thanks for the debug build. I'll run that and report back ASAP.It will be useful to check a TCI issue I had also, hopefully after I identify the current issue
|
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 17:11:07 GMT
Ok took a few tries to get 160 going and nothing seems to be recorded in either log while JTDX is trying to start, perhaps that's normal? I've attached both files for reference in case anything stands out as my knowledge is pretty limited when it comes to code . Attachments:jtdx_debug.txt (26.29 KB)
JTDX_trace.log (187.38 KB)
|
|
|
|
Post by w9mdb on Mar 29, 2022 17:23:36 GMT
Did you try the powershell commands to list all the dlls loaded and see if any other Qt libraries are running?
|
|
|
|
Post by Tony Ei7bmb on Mar 29, 2022 18:31:23 GMT
Not figured that part out yet but will do some googling
|
|
