--prefetch --dry-run intermittently hangs with a large number of dependencies - Windows #1689

Closed
enolan opened this Issue Jan 21, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@enolan
Contributor

enolan commented Jan 21, 2016

Sometimes, when I run stack build --only-snapshot --prefetch --dry-run Stack hangs after the last download message is printed. Process Explorer and Resource Monitor report there are no network connections open, stack.exe is using ~12% CPU which corresponds to pegging one virtual core on my machine, and the vast majority of the CPU time is spent in kernel. The active thread, according to Process Explorer, is in ntdll.dll!ZwDeviceIoControlFile+0xa most of the time.

To reproduce:

Here's a log https://gist.github.com/enolan/25aad1613c42fee5fcbf

@enolan enolan changed the title from --prefetch --dry-run hangs with a large number of dependencies - Windows to --prefetch --dry-run intermittently hangs with a large number of dependencies - Windows Jan 21, 2016

@mgsloan

This comment has been minimized.

Show comment
Hide comment
@mgsloan

mgsloan May 20, 2016

Collaborator

Wow, thanks for figuring out the GHC issue and writing a blogpost about it!! http://www.echonolan.net/posts/2016-05-10-a-debugging-horror-story.html

Hopefully there will be a GHC release soon with the fix. Once released, I wonder if we should only release the windows version compiled with that GHC.

Collaborator

mgsloan commented May 20, 2016

Wow, thanks for figuring out the GHC issue and writing a blogpost about it!! http://www.echonolan.net/posts/2016-05-10-a-debugging-horror-story.html

Hopefully there will be a GHC release soon with the fix. Once released, I wonder if we should only release the windows version compiled with that GHC.

@enolan

This comment has been minimized.

Show comment
Hide comment
@enolan

enolan Jun 2, 2016

Contributor

@mgsloan The fix didn't make it into GHC 8.0 unfortunately. :(

I wrote a workaround in network but that has its own problem - another crash. I might have added it when doing the workaround, or it may have always been there. Here's the network PR if anyone wants to take a look: haskell/network#192. If you can tell me why it's still crashing I'd be happy.

Contributor

enolan commented Jun 2, 2016

@mgsloan The fix didn't make it into GHC 8.0 unfortunately. :(

I wrote a workaround in network but that has its own problem - another crash. I might have added it when doing the workaround, or it may have always been there. Here's the network PR if anyone wants to take a look: haskell/network#192. If you can tell me why it's still crashing I'd be happy.

@mgsloan

This comment has been minimized.

Show comment
Hide comment
@mgsloan

mgsloan Mar 18, 2017

Collaborator

Closing as an upstream issue

Collaborator

mgsloan commented Mar 18, 2017

Closing as an upstream issue

@mgsloan mgsloan closed this Mar 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment