Performance issue bottleneck when scanning new drive - OutputDebugStringW

[golosovsky]

I've just added Google Drive (on my Windows PC - drive G) to Everything's index.
When examining Everything's performance via Sysinternals procmon -- I've noticed that a huge chunk of the CPU time was "wasted" on calling OutputDebugStringW WinAPI, which is invoked by DllInstall WinAPI.

So, I wander if it's Everything or Google Drive to blame?
Is there a way to avoid this, in your opinion?

I'm attaching a screenshot of Sysinternals procmon "Stack Summary" for that session:


As you can see in the screenshot -- it seems that Google Drive is the one to blame for the DllInstall calls. But, maybe this entire "code path" can be avoided in some way by Everything.

[EricB]

@golosovsky

In the past I've also seen lagging behaviour of Everything 1.4 in combination with Google Drive. After changing to Everything 1.5a this does not occur anymore.

Regards, EricB

[void]

Everything doesn't use OutputDebugString.

Please try Sysinternal's DebugView to view the debug output.

What message is being logged? -this might give a clue to what is calling OutputDebugString.