hGetBufSome: resource exhausted Issue on Windows 7

[cricrazy]

I installed pandoc on Windows7 (64bit) using the installer on the pandoc website. When I try to run pandoc from command prompt. This is the error I got.

C:\Users\cricrazy>pandoc
pandoc: : hGetBufSome: resource exhausted (Not enough space)

Plz Help.

[jgm]

I haven't seen this before. Does pandoc immediately return with this error when you run it without arguments? Or did you terminate standard input with Ctrl-Z? Can you also try pandoc --version and run pandoc with a file argument?

[cricrazy]

Thanks John.

I took a screenshot of pandoc --version. I am attaching it here. I used the pandoc with the file argument and it works perfectly. I suppose, when I tried pandoc without any arguments, I got the above error.

Thanks for your help.

[jgm]

You didn't answer this question: " Does pandoc immediately return with this error when you run it without arguments? Or did you terminate standard input with Ctrl-Z?"

[arnoesterhuizen]

I've also encountered this error, and pandoc returns with this error immediately. I then discovered I didn't specify the input file, so it might be a similar problem.

[cricrazy]

@jgm
It does return this error when I run without any arguments. I was not trying to terminate it with Ctrl-Z.
thanks.

[jgm]

It would be really helpful to know whether you experience the same with earlier versions of pandoc. Can you try uninstalling pandoc and installing an earlier version? I am curious whether you see the same problem with 1.9.4.2,
1.10, 1.11. This would give valuable clues about where the problem lies.

[mrmagooey]

I get the same behaviour with 1.11.1 and 1.10. 1.9 I can run without the error. I am on Windows 7.

[jgm]

Thanks @mrmagooey, that is helpful indeed. It suggests that the problem started with the following change in 1.0: "We no longer depend on utf8-string. Instead we use functions defined in Text.Pandoc.UTF8 that use Data.Text’s conversions."

[jgm]

I created an EC2 instance running Windows 8 64-bit, and installed the latest Haskell Platform.
In GHCI I can confirm that

Data.ByteString.Lazy.hGetContents stdin

returns the error "hGetBufSome: resource exhausted (Not enough space)", while

Data.ByteString.hGetContents stdin

works fine. This suggests that the problem could be fixed by using strict instead of lazy bytestrings for input in Text.Pandoc.UTF8.

[jgm]

Compiling the existing code on a Windows 64 box (Windows server 12 EC2 instance) also seems to fix the problem. The resulting binary runs on both 32-bit and 64-bit Windows. So the best solution going forward may be for me to move my build operation.

[jgm]

Correction to last comment: on my Windows 12 Server 64-bit instance, I can't reproduce any of the problems I saw on 64-bit Windows 8 server. The new binary works well, but so do the old ones (e.g. 1.10.x). And I can't reproduce the problem seen above in GHCI. Unfortunately, this problem seems to arise for a very specific class of machines/OSs.

[jgm]

OK - I'll just use strict bytestrings. That should solve the problem.

[jgm]

I can confirm that a binary produced with this patch works on Windows 8 server, 64-bit.