c++ - Why does my program consume 100% CPU under nVidia NView? -


Text after "div class =" itemprop = "text">

I have a recent Windows program that will sometimes not respond when scrolling a large list of items in the output environment Was working on. Of course this works fine on my desktop.

  • Note that Windows XP based 2 monitors
  • n with NVIDIA video driver enabled
  • < The work environment is with: The production environment is the Dr. Watson Stack Trace that occurs when the process ends: State Dump for Thread Id 0xef4 eax = 00e3fff8 EBX = 000000a0 ECX = 00e00000 EDX = 00000000 ESI = 0003fff8 EDI = 00e40000 EIP = 00b920c2 esp = 0012bcac EBP = 00000000 iopl = 0 NV up A ng nZ na pe cy cs = 001b ss = 0023 ds = 0023 es = 0023 FS = 003B gs = 0000 EFL = 00,000,283 \ system32 \ nview.dll - Function: n here enter NVLoadDatabase 00b920a8 c80b0600 0x60b, 0x0 00b920ac 83c30f ebayx, 0xf 00b920af 33f6 xor esi, esi 00b920b1 03f 9 edi, Ecx 00b920b3 83e3f8 and ebayx, 0xfffffff8 00b920b6 3bcf cmp ecx, edi 00b920b8 89742414 mov [esp + 0x14], esi 00b920bc 734c jnb nview! NVLoadDatabase + 0xcaf Add 0 0b9210a) 00b920be 8bc1 mov eax, ecx 00b920c0 8b10 mov edx, [eax] 00b920c2 8b4004 mov eax, [eax + 0x4] ds: 0023: 00e3fffc = 00000000 00b920c5 89442414 mov [esp + 0x14], eax 00b920c9 8bc2 mov eax, edx 00b920cb 2500000001 and eX, 0x1000000 00b920d0 33d xor ebp, ebp 00b920d2 0bc5 or eax, ebp 00b920d4 7414 jz nview! NVLoadDatabase + 0xc8f (00b920ea) 00b920d6 8bc2 mov eax, edx 00b920d8 c1e008 slax, 0x8 00b920db 8be8 mov ebp, eax 00b920dd c1f81f sar eax, 0x1f ChildEBP RetAddr args child to 00000000 00000000 00000000 00000000 00000000 n here! NVLoadDatabase + 0xc67

    Why did this problem only happen in production?

This is interested because the nView is a third party DLL provided by Nvid nview! Posting on the Internet about NVLoadDatabase suggests that there is an unauthorized flaw in the NNV. It is supported by the fact that Explorer uses 100% of CPU, as confirmed by these reports. See:

A detailed investigation of this problem is available on this site:

According to this article, the hang is due to the infinite loop in a nview.dll. Although assembly instructions and really did not match descriptions in our logs, register the values ​​described online, they were quite close to me to conclude that it was the same issue.

To solve the problem, I disabled the Disabled Desktop Manager (right click on desktop, select nView property, and click Disable in the nView Desktop Manager group box). Before doing so I was able to reposition the hanging constantly. However, after disabling nView I could not reproduce the hang. Thus, it appears to be a viable alternative solution.

However, I have posted it here, if it would be useful to anyone, I am very sad to chase this one.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -