mariusvam / windows-package-manager

Automatically exported from code.google.com/p/windows-package-manager
1 stars 0 forks source link

Applications hangs at 'Detecting MSI packages' #220

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
As the summary states, I open npackd. It downloads the repository at the 
'Initializing / Loading repositories / Detecting software / Detecting MSI 
packages' it just hangs. 

I'm also unable to quit the program because it says 'Cannot exit while jobs are 
running'. So the application is still responsive, it just never finishes with 
the MSI packages.

Original issue reported on code.google.com by igi...@gmail.com on 9 Apr 2013 at 10:05

GoogleCodeExporter commented 8 years ago
Please export using regedit.exe and upload here the following sub-trees:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall ,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall ,
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninsta
ll ,
and
HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstal
l

Original comment by tim.lebe...@gmail.com on 9 Apr 2013 at 7:40

GoogleCodeExporter commented 8 years ago
Attached.

HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstal
l didn't exist.

I'm on Windows XP 32bit.

Original comment by igi...@gmail.com on 17 Apr 2013 at 10:33

Attachments:

GoogleCodeExporter commented 8 years ago
unfortunately this did not help. 

Please do the following:
- install Process Explorer and start it
- start Npackd
- locate Npackd in the Process Explorer
- click with the right mouse button and choose "Properties" on the Npackd 
process in Process Explorer
- switch to the "Threads" tab
- select the thread that consumes the most CPU or the one with "msvcrt.dll 
+0xXXXXX". If there are more than one thread, please repeat the following 3 
steps for each of them.
- click on "Copy"
- click on "Copy All"
- upload the text here

Original comment by tim.lebe...@gmail.com on 18 Apr 2013 at 8:32

GoogleCodeExporter commented 8 years ago
I already had Process Hacker installed, so I followed a similar approach.  Let 
me know if this is insufficient.

6820, 12.28, 1, msvcrt.dll!endthreadex+0x3a, Lowest

Original comment by igi...@gmail.com on 19 Apr 2013 at 7:39

GoogleCodeExporter commented 8 years ago
No. This is not enough. I'd need something like this:
0, ntoskrnl.exe!PoStartNextPowerIrp+0x17e7
1, ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
2, ntoskrnl.exe!KeDelayExecutionThread+0x186
3, ntoskrnl.exe!NtWaitForSingleObject+0x16e
4, ntoskrnl.exe!KeSynchronizeExecution+0x3a23
5, ntdll.dll!NtDelayExecution+0xa
6, KernelBase.dll!SleepEx+0xb3
7, iPodService.exe+0x2f1c4
8, iPodService.exe+0x2ea57
9, iPodService.exe+0x12f33
10, iPodService.exe+0x4349b
11, iPodService.exe+0x4354f
12, kernel32.dll!BaseThreadInitThunk+0xd
13, ntdll.dll!RtlUserThreadStart+0x21

Please look at the attached screenshot for how to do this using the Process 
Hacker.

Original comment by tim.lebe...@gmail.com on 20 Apr 2013 at 6:20

Attachments:

GoogleCodeExporter commented 8 years ago
0, ntkrnlpa.exe!KiDeliverApc+0xb3
1, ntkrnlpa.exe!ZwYieldExecution+0x2572
2, ntkrnlpa.exe!ZwYieldExecution+0x1c90
3, hal.dll!HalClearSoftwareInterrupt+0x342
4, QtCore4.dll!ZN18QFileSystemWatcherC2ERK11QStringListP7QObject+0x1503
5, QtCore4.dll!ZN9QFileInfoC1ERK7QString+0x73
6, npackdg.exe+0x38f6d
7, npackdg.exe+0x2df21
8, npackdg.exe+0x2f809
9, npackdg.exe+0x2fcc7
10, npackdg.exe+0x30299
11, npackdg.exe+0x3072a
12, npackdg.exe+0x30c63
13, npackdg.exe+0x38ae
14, QtCore4.dll!ZN7QThread21setTerminationEnabledEb+0x218
15, msvcrt.dll!endthreadex+0xa9
16, kernel32.dll!GetModuleFileNameA+0x1ba

Original comment by igi...@gmail.com on 23 Apr 2013 at 7:34

GoogleCodeExporter commented 8 years ago
is this 1.17.9? The stack trace looks strange.

Original comment by tim.lebe...@gmail.com on 23 Apr 2013 at 6:18

GoogleCodeExporter commented 8 years ago
It was 1.17.8. I upgraded to 1.17.9 now and get this:

0, ntkrnlpa.exe!KiDeliverApc+0xb3
1, ntkrnlpa.exe!ZwYieldExecution+0x2572
2, ntkrnlpa.exe!ZwYieldExecution+0x1c90
3, hal.dll!HalClearSoftwareInterrupt+0x342
4, QtCore4.dll!ZN7QStringC1EiN2Qt14InitializationE+0x131
5, QtCore4.dll!ZNK7QString3argERKS_iRK5QChar+0x101
6, npackdg.exe+0x38966
7, npackdg.exe+0x2bf51
8, npackdg.exe+0x2d801
9, npackdg.exe+0x2dcbf
10, npackdg.exe+0x2e291
11, npackdg.exe+0x2e722
12, npackdg.exe+0x304ff
13, npackdg.exe+0x38ae
14, QtCore4.dll!ZN7QThread21setTerminationEnabledEb+0x218
15, msvcrt.dll!endthreadex+0xa9
16, kernel32.dll!GetModuleFileNameA+0x1ba

Original comment by igi...@gmail.com on 24 Apr 2013 at 10:47

GoogleCodeExporter commented 8 years ago
The reconstructed stack trace below does not contain anything special. Which 
program consumes the most CPU? Is it Npackd? How long did you wait? Could you 
run Npackd for an hour? Please check your installation directory and the 
NpackdDetected sub-directory for many almost empty directories. Try to delete 
NpackdDetected.

0, ntkrnlpa.exe!KiDeliverApc+0xb3
1, ntkrnlpa.exe!ZwYieldExecution+0x2572
2, ntkrnlpa.exe!ZwYieldExecution+0x1c90
3, hal.dll!HalClearSoftwareInterrupt+0x342
4, QtCore4.dll!ZN7QStringC1EiN2Qt14InitializationE+0x131
5, QtCore4.dll!ZNK7QString3argERKS_iRK5QChar+0x101
6, npackdg.exe+0x38966 WPMUtils::findNonExistingFile(QString const&)
7, npackdg.exe+0x2bf51 Repository::detectOneControlPanelProgram(QString const&, 
WindowsRegistry&, QString const&, QStringList*, QStringList*)
8, npackdg.exe+0x2d801 Repository::detectControlPanelProgramsFrom(HKEY__*, 
QString const&, bool, QStringList*, QStringList*)
9, npackdg.exe+0x2dcbf Repository::detectControlPanelPrograms()
10, npackdg.exe+0x2e291 Repository::detect(Job*)
11, npackdg.exe+0x2e722 Repository::refresh(Job*)
12, npackdg.exe+0x304ff Repository::reload(Job*, bool)
13, npackdg.exe+0x38ae InstallThread::run()
14, QtCore4.dll!ZN7QThread21setTerminationEnabledEb+0x218
15, msvcrt.dll!endthreadex+0xa9
16, kernel32.dll!GetModuleFileNameA+0x1ba

Original comment by tim.lebe...@gmail.com on 25 Apr 2013 at 5:29

GoogleCodeExporter commented 8 years ago
Yay, deleting NpackdDetected solved the issue. Now the startup process runs 
through quickly. Thanks.

It did bring up another issue. I was unable to quit Npackd (as mentioned in the 
first comment). It also happens sometimes when there is a network issue and the 
.xml file can't be downloaded successfully. The connection stalls, but I'm 
unable to quit Npackd other than killing it from a task manager. Should I log a 
new bug?

Original comment by igi...@gmail.com on 26 Apr 2013 at 6:49

GoogleCodeExporter commented 8 years ago
Oh wait, problem not solved. If I delete NpackdDetected, it works the next 
time. But every time after that it hangs again.

npackdg.exe consumes the most CPU (12.5%, which is one full core). 

I let it run for 3 hours and it still hung.

Original comment by igi...@gmail.com on 26 Apr 2013 at 1:48

GoogleCodeExporter commented 8 years ago
Thank you very much for the help.

You can file another issue, if you wish. 

Could you please create another stack trace to be completely sure we search in 
the right direction? 

Please also upload here the NpackdDetected directory (as a .zip).

Original comment by tim.lebe...@gmail.com on 27 Apr 2013 at 6:59

GoogleCodeExporter commented 8 years ago
Attached.

Original comment by igi...@gmail.com on 29 Apr 2013 at 7:43

Attachments:

GoogleCodeExporter commented 8 years ago
Could you please create another stack trace to be completely sure we search in 
the right direction? 

Original comment by tim.lebe...@gmail.com on 9 May 2013 at 6:31

GoogleCodeExporter commented 8 years ago
0, ntkrnlpa.exe!KiDeliverApc+0xb3
1, ntkrnlpa.exe!ZwYieldExecution+0x2572
2, ntkrnlpa.exe!ZwYieldExecution+0x1c90
3, hal.dll!HalClearSoftwareInterrupt+0x342
4, hal.dll!HalRequestSoftwareInterrupt+0x3c
5, ntkrnlpa.exe!SePrivilegeCheck+0x30
6, ntkrnlpa.exe!NtWriteFile+0x5862
7, ntkrnlpa.exe!NtWriteFile+0x5a10
8, ntkrnlpa.exe!NtMakePermanentObject+0x11b2
9, ntkrnlpa.exe!ObOpenObjectByName+0xea
10, ntkrnlpa.exe!NtDeleteFile+0x522
11, ntkrnlpa.exe!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb74
12, ntdll.dll!KiFastSystemCallRet
13, QtCore4.dll!ZN18QWindowsPipeWriter5writeEPKcx+0x403f
14, QtCore4.dll!ZNK9QFileInfo6existsEv+0x6e
15, npackdg.exe+0x38977
16, npackdg.exe+0x2bf51
17, npackdg.exe+0x2d801
18, npackdg.exe+0x2dcbf
19, npackdg.exe+0x2e291
20, npackdg.exe+0x2e722
21, npackdg.exe+0x304ff
22, npackdg.exe+0x38ae
23, QtCore4.dll!ZN7QThread21setTerminationEnabledEb+0x218
24, msvcrt.dll!endthreadex+0xa9
25, kernel32.dll!GetModuleFileNameA+0x1ba

I also attach a screenshot.

Original comment by igi...@gmail.com on 10 May 2013 at 6:40

Attachments:

GoogleCodeExporter commented 8 years ago
Reconstructed stack trace:
0, ntkrnlpa.exe!KiDeliverApc+0xb3
1, ntkrnlpa.exe!ZwYieldExecution+0x2572
2, ntkrnlpa.exe!ZwYieldExecution+0x1c90
3, hal.dll!HalClearSoftwareInterrupt+0x342
4, hal.dll!HalRequestSoftwareInterrupt+0x3c
5, ntkrnlpa.exe!SePrivilegeCheck+0x30
6, ntkrnlpa.exe!NtWriteFile+0x5862
7, ntkrnlpa.exe!NtWriteFile+0x5a10
8, ntkrnlpa.exe!NtMakePermanentObject+0x11b2
9, ntkrnlpa.exe!ObOpenObjectByName+0xea
10, ntkrnlpa.exe!NtDeleteFile+0x522
11, ntkrnlpa.exe!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb74
12, ntdll.dll!KiFastSystemCallRet
13, QtCore4.dll!ZN18QWindowsPipeWriter5writeEPKcx+0x403f
14, QtCore4.dll!ZNK9QFileInfo6existsEv+0x6e
15, npackdg.exe+0x38977 WPMUtils::findNonExistingFile(QString const&)
16, npackdg.exe+0x2bf51 Repository::detectOneControlPanelProgram(QString 
const&, WindowsRegistry&, QString const&, QStringList*, QStringList*)
17, npackdg.exe+0x2d801 Repository::detectControlPanelProgramsFrom(HKEY__*, 
QString const&, bool, QStringList*, QStringList*)
18, npackdg.exe+0x2dcbf Repository::detectControlPanelPrograms()
19, npackdg.exe+0x2e291 Repository::detect(Job*)
20, npackdg.exe+0x2e722 Repository::refresh(Job*)
21, npackdg.exe+0x304ff Repository::reload(Job*, bool)
22, npackdg.exe+0x38ae InstallThread::run()
23, QtCore4.dll!ZN7QThread21setTerminationEnabledEb+0x218
24, msvcrt.dll!endthreadex+0xa9
25, kernel32.dll!GetModuleFileNameA+0x1ba

Original comment by tim.lebe...@gmail.com on 20 May 2013 at 2:16

GoogleCodeExporter commented 8 years ago

Original comment by tim.lebe...@gmail.com on 1 Jun 2013 at 10:31

GoogleCodeExporter commented 8 years ago
1.18.3 Alpha:

https://code.google.com/p/windows-package-manager/downloads/list?can=1&q=1.18.3&
colspec=Filename+Summary+Uploaded+ReleaseDate+Size+DownloadCount

Original comment by tim.lebe...@gmail.com on 11 Oct 2013 at 4:09

GoogleCodeExporter commented 8 years ago
Great, 1.18.3 alpha fixes the problem for me!

Original comment by igi...@gmail.com on 14 Oct 2013 at 4:06

GoogleCodeExporter commented 8 years ago

Original comment by tim.lebe...@gmail.com on 19 Oct 2013 at 6:28