<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rémi Denis-Courmont wrote:
<blockquote cite="mid:ac819d135a9427d161f20ea1bcea6b0b@chewa.net"
type="cite">
<pre wrap="">On Mon, 14 Sep 2009 15:40:12 +1000, xxcv <a class="moz-txt-link-rfc2396E" href="mailto:xxcv07@gmail.com"><xxcv07@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">This bug is easily triggered with in seconds of pressing or holding N.
Disregard whether qt4 GUI interface was involved it can be triggered by
using the dummy interface.
</pre>
</blockquote>
<pre wrap=""><!---->
As far as I can tell:
- we have only one developer with Win7, and he is busy,
- disassembly is totally useless to us,
- stack trace with only ?? are totally useless.
Bottom line is, your report cannot be used, and so you're wasting your
time.
</pre>
</blockquote>
I understand this. But lets be positive and keep it at the bright side,
as I'm trying to find out the exact problem, I saw.<br>
At the time of this happening:<br>
ntoskrnl.exe!IoAcquireRemoveLockEx+0xe7<br>
ntoskrnl.exe!memset+0x22a<br>
ntoskrnl.exe!KeWaitForSingleObject+0x2cb<br>
ntoskrnl.exe!KeDetachProcess+0x120d<br>
ntoskrnl.exe!PsReturnProcessNonPagedPoolQuota+0x3a3<br>
ntoskrnl.exe!CcSetDirtyPinnedData+0x433<br>
ntoskrnl.exe!ZwUnloadKeyEx+0x1162<br>
msvcrt.dll!strcpy+0x1d4<br>
libvlccore.dll!_stream_UrlNew+0x2025<br>
libvlccore.dll!_stream_UrlNew+0x1da2<br>
<br>
ntoskrnl.exe!IoAcquireRemoveLockEx+0xe7<br>
ntoskrnl.exe!memset+0x22a<br>
ntoskrnl.exe!KeWaitForSingleObject+0x2cb<br>
ntoskrnl.exe!KeDetachProcess+0x120d<br>
ntoskrnl.exe!PsReturnProcessNonPagedPoolQuota+0x3a3<br>
ntoskrnl.exe!CcSetDirtyPinnedData+0x433<br>
ntdll.dll!MD4Final+0x78b3<br>
ntdll.dll!KiUserExceptionDispatcher+0x2e<br>
msvcrt.dll!strcpy+0x1d4<br>
libvlccore.dll!_stream_UrlNew+0x2025<br>
libvlccore.dll!_stream_UrlNew+0x1da2<br>
<br>
This comes from the same thread at that time this thread utilizes full
cpu.<br>
Perhaps you'd know more then me by looking at this stack.<br>
Thanks for your kind attention.<br>
Regards<br>
</body>
</html>