On my Win7x64 laptop kid3 v3.4.1 is veeerrrry slow to start, taking many minutes from 2x clicking kid3.exe to the time the GUI displays. After loading it is responsive, with no appreciable in accessing any menu items or reading a folder with 380 mp3s. Task Manager shows kid3.exe consuming 0% CPU and 7.5MB memory, while I have 85% free CPU and 2GB free physical memory.
Any idea what the trouble is and how I can fix it?
System Summary:
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name XPS
System Manufacturer Dell Inc.
System Model Dell System XPS L502X
System Type x64-based PC
Processor Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. A09, 13/01/2012
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale Canada
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name xps\Matt
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.90 GB
Available Physical Memory 1.88 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 9.50 GB
Page File Space 7.90 GB
Page File C:\pagefile.sys
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Strange, I have never seen this. Let's try to find the cause.
Kid3 by default opens the last opened folder. Maybe it is no longer accessible or very slow. Start a command line cmd.exe, cd into the directory where kid3.exe is located and try to start it with the current directory as the directory to open:
kid3.exe .
Still slow? Maybe something with the current configuration. You can set the environment variable KID3_CONFIG_FILE to the path of a configuration file or to an invalid path to use the default configuration. While still on the command line, try this:
set KID3_CONFIG_FILE=""
kid3.exe
If this helps, try to reset the configuration to the defaults by restarting kid3.exe normally (double-clicking), then go to "Settings/Configure Kid3...", click "Restore defaults", then "OK".
Otherwise, the problem is harder. Could you try to start the Sysinternals Process Monitor, set the filter to monitor only "kid3.exe", then start Kid3 and look into Process Monitor to see what is going on while it is starting so slow. Does the problem also exist with older versions of Kid3?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for prompt response, and an engaged one at that.
No difference starting with current folder argument or setting config environment to blank. I'm experimenting with Process Monitor and will report back (first time using it). I'm filtering for "Process Name includes 'kid3' ". Initial results:
About 1s from thread start to first noticable pause point:
10:14:21.9068407 AM kid3.exe 6812 RegOpenKey HKLM\SOFTWARE\Wow6432Node\Wacom SUCCESS Desired Access: Read
10:14:21.9068599 AM kid3.exe 6812 RegSetInfoKey HKLM\SOFTWARE\Wow6432Node\Wacom SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
10:14:21.9068711 AM kid3.exe 6812 RegQueryValue HKLM\SOFTWARE\Wow6432Node\Wacom\WintabTimeout NAME NOT FOUND Length: 144
10:14:21.9068827 AM kid3.exe 6812 RegCloseKey HKLM\SOFTWARE\Wow6432Node\Wacom SUCCESS
then 5s to next one (no events in between):
10:14:26.9074066 AM kid3.exe 6812 CreateFile C:\apps\kid3\ISD_Tablet.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
10:14:26.9075592 AM kid3.exe 6812 CreateFile C:\Windows\SysWOW64\ISD_Tablet.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
10:14:26.9077691 AM kid3.exe 6812 CreateFile C:\Windows\system\ISD_Tablet.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
10:14:26.9079020 AM kid3.exe 6812 CreateFile C:\Windows\ISD_Tablet.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
10:14:26.9080322 AM kid3.exe 6812 CreateFile C:\apps\kid3\ISD_Tablet.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
Then a 7 minute pause before starting a series of registry queries (no events captured in this pause):
10:21:31.9277724 AM kid3.exe 6812 RegOpenKey HKLM\Software\Wow6432Node\Microsoft\Windows\Tablet PC\ SUCCESS Desired Access: Read
10:21:31.9278079 AM kid3.exe 6812 RegSetInfoKey HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\Tablet PC SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
10:21:31.9278223 AM kid3.exe 6812 RegQueryValue HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\Tablet PC\IsTabletPC SUCCESS Type: REG_DWORD, Length: 4, Data: 1229
Followed by 18K events occuring over 5s, at which point the GUI appears.
Most of the events seem to be registry queries and Create/Read/CloseFile operations. The listed registry keys and files don't have any obvious connection to Kid3 or Qt, things like MS Office GROOVEEX.DLL.
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe a Wacom driver issue. Google for isd_tablet.dll. Maybe installing the 32bit driver helps, see http://forum.wacom.eu/viewtopic.php?f=9&t=5125&start=10, or copying the dlls from a GIMP installation Installation.installation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
On my Win7x64 laptop kid3 v3.4.1 is veeerrrry slow to start, taking many minutes from 2x clicking kid3.exe to the time the GUI displays. After loading it is responsive, with no appreciable in accessing any menu items or reading a folder with 380 mp3s. Task Manager shows kid3.exe consuming 0% CPU and 7.5MB memory, while I have 85% free CPU and 2GB free physical memory.
Any idea what the trouble is and how I can fix it?
System Summary:
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name XPS
System Manufacturer Dell Inc.
System Model Dell System XPS L502X
System Type x64-based PC
Processor Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. A09, 13/01/2012
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale Canada
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name xps\Matt
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.90 GB
Available Physical Memory 1.88 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 9.50 GB
Page File Space 7.90 GB
Page File C:\pagefile.sys
Strange, I have never seen this. Let's try to find the cause.
Kid3 by default opens the last opened folder. Maybe it is no longer accessible or very slow. Start a command line cmd.exe, cd into the directory where kid3.exe is located and try to start it with the current directory as the directory to open:
Still slow? Maybe something with the current configuration. You can set the environment variable KID3_CONFIG_FILE to the path of a configuration file or to an invalid path to use the default configuration. While still on the command line, try this:
If this helps, try to reset the configuration to the defaults by restarting kid3.exe normally (double-clicking), then go to "Settings/Configure Kid3...", click "Restore defaults", then "OK".
Otherwise, the problem is harder. Could you try to start the Sysinternals Process Monitor, set the filter to monitor only "kid3.exe", then start Kid3 and look into Process Monitor to see what is going on while it is starting so slow. Does the problem also exist with older versions of Kid3?
Thank you for prompt response, and an engaged one at that.
No difference starting with current folder argument or setting config environment to blank. I'm experimenting with Process Monitor and will report back (first time using it). I'm filtering for "Process Name includes 'kid3' ". Initial results:
About 1s from thread start to first noticable pause point:
then 5s to next one (no events in between):
Then a 7 minute pause before starting a series of registry queries (no events captured in this pause):
Followed by 18K events occuring over 5s, at which point the GUI appears.
Most of the events seem to be registry queries and Create/Read/CloseFile operations. The listed registry keys and files don't have any obvious connection to Kid3 or Qt, things like MS Office GROOVEEX.DLL.
Matt
I can send you the process log if that helps.
Maybe a Wacom driver issue. Google for isd_tablet.dll. Maybe installing the 32bit driver helps, see http://forum.wacom.eu/viewtopic.php?f=9&t=5125&start=10, or copying the dlls from a GIMP installation Installation.installation.