Software feedback > RogueKiller

RogueKiller blocks on ProcessTree

(1/3) > >>

Tigzy:
EDIT 02/18/2014. This is not fixed. We still need debug informations please.


Hello
This is a known issue, but we are unable to fix it due to lack of information.
If you have this problem, please follow the instructions below in order to help us fixing this issue.  :)

- Download the debug version: http://www.sur-la-toile.com/RogueKiller/RogueKiller_DEBUG.exe
- Launch it.
- When it blocks, go to : %Desktop%/RK_Quarantine folder and copy the debug.log file on the desktop.
- It can be huge, so please remove all but the last 100 lines with a text editor like notepad. Save it.
- In this thread, attach this tiny report and please provide your OS information with it (Windows XP, Windows 7 64 bits/32 bits, ... )

Thanks in advance :)


thisisu:
Hi Tigzy,

Windows 7 Home Premium SP1 x64

Last 30 lines attached.

Note: It doesn't always hang. I had to launch the debug version about 6 times for it to finally hang again.

__

ProcessExplorer created a blank 0 byte .dmp file. No information to report from it.

Maybe this will help though? Stack information on RogueKiller_DEBUG.exe+0x1ea980


--- Code: ---ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xba4
ntoskrnl.exe!PoStartNextPowerIrp+0x1821
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x93d
ntoskrnl.exe!KeWaitForMutexObject+0x19f
win32k.sys!memset+0x7a47
win32k.sys!memset+0x7ae9
win32k.sys!memset+0x612c
win32k.sys!memset+0x6235
win32k.sys!memset+0x7c11
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
wow64win.dll+0x3fe3a
wow64win.dll+0x1aea8
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42b
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!DispatchMessageW+0x5c
RogueKiller_DEBUG.exe+0xfac5
RogueKiller_DEBUG.exe+0x1219
RogueKiller_DEBUG.exe+0x1eaae2
RogueKiller_DEBUG.exe+0x1ea98f
kernel32.dll!BaseThreadInitThunk+0x12
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36

--- End code ---

Tigzy:
I don't find the debug.log lines :/ Did you forget them?
What if you suspend the process with Process Explorer (context menu as well) before create the dump?

Because the stack trace is missing the symbols (that are private on my side)

thisisu:

--- Quote from: Tigzy on February 10, 2014, 08:15:23 am ---I don't find the debug.log lines :/ Did you forget them?
--- End quote ---
It's attached as debug.txt. The forums don't allow .log extension to be uploaded so I renamed it.

Tigzy:
Gotcha :)

Navigation

[0] Message Index

[#] Next page

Go to full version