Hacker News Reader

Comment by pmelendez | Hacker News Reader

> I understand that it must be trying to extract some extra "useful" information from those large files, but the keys is that it shouldnt block your UI from showing the basic stuff.

That's weird, all the file-io operations in windows store apps are async for the very reason of not blocking the UI thread. How big was that folder? I'm geniuly curious.

View on HN

Async ops can still take a long time. (Actually that's probably why they were made async.) GP wants to update the UI, but the data isn't available yet. Even if UI is still responding to mouse clicks, it hasn't yet fulfilled the user's desire to display that data, so it is blocking in a sense.

I think he refers to File Explorer (explorer.exe) which has nothing to do with Windows Store Apps.

I know but it wasn't clear to me that he was using file explorer (I haven't seen the issue on none of my machines)

What explorer will be doing is calling into a shell extension to generate the video thumbnails. Under some circumstances it ends up blocked on the shell extension.

http://blogs.technet.com/b/markrussinovich/archive/2005/08/2... (not precisely the same thing, but related)

I've personally seen opening a folder full of photos produce a crash dialog pointing the blame at an Nvidia DLL.

Explorer is not a Windows Store app.

I know but he didn't say he was using explorer to open the folder and inspect the files. I was guessing he must be using an app to show them since is the only dialog that's different (I have multi-gb video folders in my pc and haven't seen the issue). He did say he was using Win10 and the file dialog is back to be the same so my guess would be incorrect anyway.

Reply on news.ycombinator.com