errors converting docx files

errors converting docx files

[Jason Davies]

Hi folks,

I just tried to convert three short Word files one at a time; one worked 
fine but two gave errors like this:

pandoc(24405,0x209984e00) malloc: can't allocate region
:*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
malloc_error_break to debug
pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
exhausted (Cannot allocate memory)


I'm completely out of my depth here; does this seem to suggest the files 
are quirky or is it a pandoc issue (which I could more usefully report)?

Running an M1 Mac Mini on 11.3 and just reinstalled pandoc (March 20, 
2021 is the user guide date).

Thanks for any suggestions.

Cheers,

Jason

Re: errors converting docx files

[John MacFarlane]

You're converting to PDF, I gather. Do any conversions to other
formats cause problems? If it is just PDF, the problem is likely
due to the step where pandoc runs pdflatex on an intermediate
tex file.  That is also suggested by the error message
itself.  But I'm mystified as to what the problem is, exactly.
ANd I don't have an M1 mac to test on.  Can anyone else reproduce
this?

"Jason Davies" <ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi folks,
>
> I just tried to convert three short Word files one at a time; one worked 
> fine but two gave errors like this:
>
> pandoc(24405,0x209984e00) malloc: can't allocate region
> :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
> pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
> malloc_error_break to debug
> pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
> exhausted (Cannot allocate memory)
>
>
> I'm completely out of my depth here; does this seem to suggest the files 
> are quirky or is it a pandoc issue (which I could more usefully report)?
>
> Running an M1 Mac Mini on 11.3 and just reinstalled pandoc (March 20, 
> 2021 is the user guide date).
>
> Thanks for any suggestions.
>
> Cheers,
>
> Jason
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/274588F4-8776-42E2-A982-3B8FAA3472C2%40gmail.com.

Re: errors converting docx files

[BPJ]

[-- Attachment #1: Type: text/plain, Size: 2735 bytes --]

Is --pdf-engine=xelatex helpful?

The LaTeX runs will take longer though.

Den fre 7 maj 2021 01:22John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:

>
> You're converting to PDF, I gather. Do any conversions to other
> formats cause problems? If it is just PDF, the problem is likely
> due to the step where pandoc runs pdflatex on an intermediate
> tex file.  That is also suggested by the error message
> itself.  But I'm mystified as to what the problem is, exactly.
> ANd I don't have an M1 mac to test on.  Can anyone else reproduce
> this?
>
> "Jason Davies" <ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Hi folks,
> >
> > I just tried to convert three short Word files one at a time; one worked
> > fine but two gave errors like this:
> >
> > pandoc(24405,0x209984e00) malloc: can't allocate region
> > :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in
> > malloc_error_break to debug
> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource
> > exhausted (Cannot allocate memory)
> >
> >
> > I'm completely out of my depth here; does this seem to suggest the files
> > are quirky or is it a pandoc issue (which I could more usefully report)?
> >
> > Running an M1 Mac Mini on 11.3 and just reinstalled pandoc (March 20,
> > 2021 is the user guide date).
> >
> > Thanks for any suggestions.
> >
> > Cheers,
> >
> > Jason
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/274588F4-8776-42E2-A982-3B8FAA3472C2%40gmail.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/m2fsyza1nx.fsf%40johnmacfarlane.net
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhARRDKJZea27J0_vxyMiB%2B57ASNQkiqkEeJBUjs1ztoDQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 4195 bytes --]

Re: errors converting docx files

[Philipp]

[-- Attachment #1.1: Type: text/plain, Size: 3469 bytes --]

I'm afraid I don't know the cause or solution of this problem, but I do 
encounter the same error from time to time when trying to create beamer 
slides with pandoc from markdown (using XeTeX).
Two things might be of interest: First, iirc, the problem first occurred 
after one of the latest macOS updates (I think it was the update to 11.3 
and not 11.3.1, but I'm not entirely sure). Second, the problem only occurs 
from time to time. Most of the time, building the slides works fine. Even 
if it occurs, a second run directly afterwards normally succeeds.
Unfortunately, I wasn't able to reproduce the problem up to now.

BP schrieb am Freitag, 7. Mai 2021 um 19:34:21 UTC+2:

> Is --pdf-engine=xelatex helpful?
>
> The LaTeX runs will take longer though.
>
> Den fre 7 maj 2021 01:22John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:
>
>>
>> You're converting to PDF, I gather. Do any conversions to other
>> formats cause problems? If it is just PDF, the problem is likely
>> due to the step where pandoc runs pdflatex on an intermediate
>> tex file.  That is also suggested by the error message
>> itself.  But I'm mystified as to what the problem is, exactly.
>> ANd I don't have an M1 mac to test on.  Can anyone else reproduce
>> this?
>>
>> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > Hi folks,
>> >
>> > I just tried to convert three short Word files one at a time; one 
>> worked 
>> > fine but two gave errors like this:
>> >
>> > pandoc(24405,0x209984e00) malloc: can't allocate region
>> > :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
>> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
>> > malloc_error_break to debug
>> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
>> > exhausted (Cannot allocate memory)
>> >
>> >
>> > I'm completely out of my depth here; does this seem to suggest the 
>> files 
>> > are quirky or is it a pandoc issue (which I could more usefully report)?
>> >
>> > Running an M1 Mac Mini on 11.3 and just reinstalled pandoc (March 20, 
>> > 2021 is the user guide date).
>> >
>> > Thanks for any suggestions.
>> >
>> > Cheers,
>> >
>> > Jason
>> >
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups "pandoc-discuss" group.
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/274588F4-8776-42E2-A982-3B8FAA3472C2%40gmail.com
>> .
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "pandoc-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/m2fsyza1nx.fsf%40johnmacfarlane.net
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9d22d67f-fa8f-4989-84a6-344f7527e0fan%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5621 bytes --]

Re: errors converting docx files

[Julio Vera]

[-- Attachment #1.1: Type: text/plain, Size: 4069 bytes --]

Hi I just want to say same thing is happening to me. 

MacBook Air M1 16GB RAM with macOS Big Sur 11.4.

I'm trying to convert a .md to beamer slides using the following command:

pandoc -t beamer -s presproy.md -o prespoy.pdf

I have to try it like 10 times or more until I get the pdf.

El domingo, 16 de mayo de 2021 a las 9:19:35 UTC-5, philipp.ku...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 
escribió:

> I'm afraid I don't know the cause or solution of this problem, but I do 
> encounter the same error from time to time when trying to create beamer 
> slides with pandoc from markdown (using XeTeX).
> Two things might be of interest: First, iirc, the problem first occurred 
> after one of the latest macOS updates (I think it was the update to 11.3 
> and not 11.3.1, but I'm not entirely sure). Second, the problem only occurs 
> from time to time. Most of the time, building the slides works fine. Even 
> if it occurs, a second run directly afterwards normally succeeds.
> Unfortunately, I wasn't able to reproduce the problem up to now.
>
> BP schrieb am Freitag, 7. Mai 2021 um 19:34:21 UTC+2:
>
>> Is --pdf-engine=xelatex helpful?
>>
>> The LaTeX runs will take longer though.
>>
>> Den fre 7 maj 2021 01:22John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:
>>
>>>
>>> You're converting to PDF, I gather. Do any conversions to other
>>> formats cause problems? If it is just PDF, the problem is likely
>>> due to the step where pandoc runs pdflatex on an intermediate
>>> tex file.  That is also suggested by the error message
>>> itself.  But I'm mystified as to what the problem is, exactly.
>>> ANd I don't have an M1 mac to test on.  Can anyone else reproduce
>>> this?
>>>
>>> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>
>>> > Hi folks,
>>> >
>>> > I just tried to convert three short Word files one at a time; one 
>>> worked 
>>> > fine but two gave errors like this:
>>> >
>>> > pandoc(24405,0x209984e00) malloc: can't allocate region
>>> > :*** mach_vm_map(size=1048576, flags: 100) failed (error 
>>> code=268435465)
>>> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
>>> > malloc_error_break to debug
>>> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
>>> > exhausted (Cannot allocate memory)
>>> >
>>> >
>>> > I'm completely out of my depth here; does this seem to suggest the 
>>> files 
>>> > are quirky or is it a pandoc issue (which I could more usefully 
>>> report)?
>>> >
>>> > Running an M1 Mac Mini on 11.3 and just reinstalled pandoc (March 20, 
>>> > 2021 is the user guide date).
>>> >
>>> > Thanks for any suggestions.
>>> >
>>> > Cheers,
>>> >
>>> > Jason
>>> >
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups "pandoc-discuss" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/pandoc-discuss/274588F4-8776-42E2-A982-3B8FAA3472C2%40gmail.com
>>> .
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "pandoc-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/pandoc-discuss/m2fsyza1nx.fsf%40johnmacfarlane.net
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/7b1d1b0a-f552-44a8-b089-6efe3f0fe8d5n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 6200 bytes --]

Re: errors converting to PDF ["can't allocate region"]

[John MacFarlane]

"Jason Davies" <ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi folks,
>
> I just tried to convert three short Word files one at a time; one worked 
> fine but two gave errors like this:
>
> pandoc(24405,0x209984e00) malloc: can't allocate region
> :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
> pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
> malloc_error_break to debug
> pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
> exhausted (Cannot allocate memory)
>

I just got an M1 mac, and I ran into this same error.

I found that if I fully specify the pdflatex path, it works:

pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex

It's a bit mysterious why this should be needed, since
`which pdflatex` returns this path!
And running pandoc with --verbose shows that the PATH is
correctly passed through to the process running pdflatex.

Anyone have any ideas?  AT least this gives a workaround...

Re: errors converting to PDF ["can't allocate region"]

[Allan Kelly]

[-- Attachment #1.1: Type: text/plain, Size: 2388 bytes --]

Great to find this posting.

I've been having this problem ever since I got a M1 MacBook Air with BigSur 
at the start of the year.

I couldn't find any references when I encountered it and put it down to 
something to do with BigSur and ARM.
I've reinstalled Pandoc and PdfLatex several time but never resolved.
I've just don't another reinstall and then stumbled on John's fix which 
works for me - thanks!

Something I noticed in the process: a really small file will process 
correctly:

# Hello world

## Hello world

### Hello world

Hello world

pandoc hello.txt -o hello.pdf 

Works.
You can add a few more paragraphs (approx 5) to hello.txt before I get the 
error - which hints that there is some actual resource exhausted happening. 
But why would that be fixed by specifying the path? Dunno.

Thanks for the fix, hope we can find a solution before long

allan


On Wednesday, 9 June 2021 at 16:40:37 UTC+1 John MacFarlane wrote:

> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Hi folks,
> >
> > I just tried to convert three short Word files one at a time; one worked 
> > fine but two gave errors like this:
> >
> > pandoc(24405,0x209984e00) malloc: can't allocate region
> > :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
> > malloc_error_break to debug
> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
> > exhausted (Cannot allocate memory)
> >
>
> I just got an M1 mac, and I ran into this same error.
>
> I found that if I fully specify the pdflatex path, it works:
>
> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex
>
> It's a bit mysterious why this should be needed, since
> `which pdflatex` returns this path!
> And running pandoc with --verbose shows that the PATH is
> correctly passed through to the process running pdflatex.
>
> Anyone have any ideas? AT least this gives a workaround...
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c6639d65-1825-47b2-861e-f946d55aaf9en%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3360 bytes --]

Re: errors converting to PDF ["can't allocate region"]

[Lewis Westbury]

[-- Attachment #1.1: Type: text/plain, Size: 3049 bytes --]

I appreciate this isn't the simple solution that you might be hoping for, 
but I've had success in getting pandoc to run reliably in a docker 
container.

I'm using it to build my thesis, and I created a template project here 
https://github.com/instantiator/markdown-thesis-builder which contains a 
sample Dockerfile, and the build script that uses pandoc.

I hope it's helpful - I found it's the only way to reliably run pandoc on 
my M1 Mac.

On Friday, 23 July 2021 at 15:53:16 UTC+1 allank...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

> Great to find this posting.
>
> I've been having this problem ever since I got a M1 MacBook Air with 
> BigSur at the start of the year.
>
> I couldn't find any references when I encountered it and put it down to 
> something to do with BigSur and ARM.
> I've reinstalled Pandoc and PdfLatex several time but never resolved.
> I've just don't another reinstall and then stumbled on John's fix which 
> works for me - thanks!
>
> Something I noticed in the process: a really small file will process 
> correctly:
>
> # Hello world
>
> ## Hello world
>
> ### Hello world
>
> Hello world
>
> pandoc hello.txt -o hello.pdf 
>
> Works.
> You can add a few more paragraphs (approx 5) to hello.txt before I get the 
> error - which hints that there is some actual resource exhausted happening. 
> But why would that be fixed by specifying the path? Dunno.
>
> Thanks for the fix, hope we can find a solution before long
>
> allan
>
>
> On Wednesday, 9 June 2021 at 16:40:37 UTC+1 John MacFarlane wrote:
>
>> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: 
>>
>> > Hi folks, 
>> > 
>> > I just tried to convert three short Word files one at a time; one 
>> worked 
>> > fine but two gave errors like this: 
>> > 
>> > pandoc(24405,0x209984e00) malloc: can't allocate region 
>> > :*** mach_vm_map(size=1048576, flags: 100) failed (error 
>> code=268435465) 
>> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
>> > malloc_error_break to debug 
>> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
>> > exhausted (Cannot allocate memory) 
>> > 
>>
>> I just got an M1 mac, and I ran into this same error. 
>>
>> I found that if I fully specify the pdflatex path, it works: 
>>
>> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex 
>>
>> It's a bit mysterious why this should be needed, since 
>> `which pdflatex` returns this path! 
>> And running pandoc with --verbose shows that the PATH is 
>> correctly passed through to the process running pdflatex. 
>>
>> Anyone have any ideas? AT least this gives a workaround... 
>>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d58296d7-cc69-460c-8445-ca359c7f006fn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4246 bytes --]

Re: errors converting to PDF ["can't allocate region"]

[SlyFox]

[-- Attachment #1.1: Type: text/plain, Size: 3536 bytes --]

M1 Mac. 

I tried this:for f in *.md; do pandoc "$f" -o "${f%.md}.pdf"; done

But I get an error:

pandoc(45574,0x207810e00) malloc: *** set a breakpoint in 
malloc_error_break to debug

pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
exhausted (Cannot allocate memory)

On Sunday, July 25, 2021 at 7:22:06 PM UTC+4 instan...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

> I appreciate this isn't the simple solution that you might be hoping for, 
> but I've had success in getting pandoc to run reliably in a docker 
> container.
>
> I'm using it to build my thesis, and I created a template project here 
> https://github.com/instantiator/markdown-thesis-builder which contains a 
> sample Dockerfile, and the build script that uses pandoc.
>
> I hope it's helpful - I found it's the only way to reliably run pandoc on 
> my M1 Mac.
>
> On Friday, 23 July 2021 at 15:53:16 UTC+1 allank...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>
>> Great to find this posting.
>>
>> I've been having this problem ever since I got a M1 MacBook Air with 
>> BigSur at the start of the year.
>>
>> I couldn't find any references when I encountered it and put it down to 
>> something to do with BigSur and ARM.
>> I've reinstalled Pandoc and PdfLatex several time but never resolved.
>> I've just don't another reinstall and then stumbled on John's fix which 
>> works for me - thanks!
>>
>> Something I noticed in the process: a really small file will process 
>> correctly:
>>
>> # Hello world
>>
>> ## Hello world
>>
>> ### Hello world
>>
>> Hello world
>>
>> pandoc hello.txt -o hello.pdf 
>>
>> Works.
>> You can add a few more paragraphs (approx 5) to hello.txt before I get 
>> the error - which hints that there is some actual resource exhausted 
>> happening. But why would that be fixed by specifying the path? Dunno.
>>
>> Thanks for the fix, hope we can find a solution before long
>>
>> allan
>>
>>
>> On Wednesday, 9 June 2021 at 16:40:37 UTC+1 John MacFarlane wrote:
>>
>>> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: 
>>>
>>> > Hi folks, 
>>> > 
>>> > I just tried to convert three short Word files one at a time; one 
>>> worked 
>>> > fine but two gave errors like this: 
>>> > 
>>> > pandoc(24405,0x209984e00) malloc: can't allocate region 
>>> > :*** mach_vm_map(size=1048576, flags: 100) failed (error 
>>> code=268435465) 
>>> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
>>> > malloc_error_break to debug 
>>> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
>>> > exhausted (Cannot allocate memory) 
>>> > 
>>>
>>> I just got an M1 mac, and I ran into this same error. 
>>>
>>> I found that if I fully specify the pdflatex path, it works: 
>>>
>>> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex 
>>>
>>> It's a bit mysterious why this should be needed, since 
>>> `which pdflatex` returns this path! 
>>> And running pandoc with --verbose shows that the PATH is 
>>> correctly passed through to the process running pdflatex. 
>>>
>>> Anyone have any ideas? AT least this gives a workaround... 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/264288c6-47ab-4d1f-9d4f-070860bdac82n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5219 bytes --]

Re: errors converting to PDF ["can't allocate region"]

[SlyFox]

[-- Attachment #1.1: Type: text/plain, Size: 1677 bytes --]

So how do you combine the two commands to batch convert?

for f in *.md; do pandoc "$f" -s -o "${f%.txt}.pdf"; done

--pdf-engine=/Library/TeX/texbin/pdflatex

On Wednesday, June 9, 2021 at 7:40:37 PM UTC+4 John MacFarlane wrote:

> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Hi folks,
> >
> > I just tried to convert three short Word files one at a time; one worked 
> > fine but two gave errors like this:
> >
> > pandoc(24405,0x209984e00) malloc: can't allocate region
> > :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
> > malloc_error_break to debug
> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
> > exhausted (Cannot allocate memory)
> >
>
> I just got an M1 mac, and I ran into this same error.
>
> I found that if I fully specify the pdflatex path, it works:
>
> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex
>
> It's a bit mysterious why this should be needed, since
> `which pdflatex` returns this path!
> And running pandoc with --verbose shows that the PATH is
> correctly passed through to the process running pdflatex.
>
> Anyone have any ideas? AT least this gives a workaround...
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c70c1da4-1ec9-4d34-aed3-7abf1c689adan%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2419 bytes --]

Re: errors converting to PDF ["can't allocate region"]

[John MacFarlane]

for f in *.md; do pandoc --pdf-engine=/Library/TeX/texbin/pdflatex "$f" -s -o "${f%.txt}.pdf"; done

SlyFox <ivan.clinical-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> So how do you combine the two commands to batch convert?
>
> for f in *.md; do pandoc "$f" -s -o "${f%.txt}.pdf"; done
>
> --pdf-engine=/Library/TeX/texbin/pdflatex
>
> On Wednesday, June 9, 2021 at 7:40:37 PM UTC+4 John MacFarlane wrote:
>
>> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > Hi folks,
>> >
>> > I just tried to convert three short Word files one at a time; one worked 
>> > fine but two gave errors like this:
>> >
>> > pandoc(24405,0x209984e00) malloc: can't allocate region
>> > :*** mach_vm_map(size=1048576, flags: 100) failed (error code=268435465)
>> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
>> > malloc_error_break to debug
>> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: resource 
>> > exhausted (Cannot allocate memory)
>> >
>>
>> I just got an M1 mac, and I ran into this same error.
>>
>> I found that if I fully specify the pdflatex path, it works:
>>
>> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex
>>
>> It's a bit mysterious why this should be needed, since
>> `which pdflatex` returns this path!
>> And running pandoc with --verbose shows that the PATH is
>> correctly passed through to the process running pdflatex.
>>
>> Anyone have any ideas? AT least this gives a workaround...
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c70c1da4-1ec9-4d34-aed3-7abf1c689adan%40googlegroups.com.

Re: errors converting to PDF ["can't allocate region"]

[SlyFox]

[-- Attachment #1.1: Type: text/plain, Size: 2506 bytes --]

This works! Thank you!

On Monday, August 2, 2021 at 2:15:33 AM UTC+4 John MacFarlane wrote:

>
> for f in *.md; do pandoc --pdf-engine=/Library/TeX/texbin/pdflatex "$f" -s 
> -o "${f%.txt}.pdf"; done
>
> SlyFox <ivan.c...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > So how do you combine the two commands to batch convert?
> >
> > for f in *.md; do pandoc "$f" -s -o "${f%.txt}.pdf"; done
> >
> > --pdf-engine=/Library/TeX/texbin/pdflatex
> >
> > On Wednesday, June 9, 2021 at 7:40:37 PM UTC+4 John MacFarlane wrote:
> >
> >> "Jason Davies" <ophi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> >>
> >> > Hi folks,
> >> >
> >> > I just tried to convert three short Word files one at a time; one 
> worked 
> >> > fine but two gave errors like this:
> >> >
> >> > pandoc(24405,0x209984e00) malloc: can't allocate region
> >> > :*** mach_vm_map(size=1048576, flags: 100) failed (error 
> code=268435465)
> >> > pandoc(24405,0x209984e00) malloc: *** set a breakpoint in 
> >> > malloc_error_break to debug
> >> > pandoc: pdflatex: createProcess: runInteractiveProcess: exec: 
> resource 
> >> > exhausted (Cannot allocate memory)
> >> >
> >>
> >> I just got an M1 mac, and I ran into this same error.
> >>
> >> I found that if I fully specify the pdflatex path, it works:
> >>
> >> pandoc -o my.pdf --pdf-engine=/Library/TeX/texbin/pdflatex
> >>
> >> It's a bit mysterious why this should be needed, since
> >> `which pdflatex` returns this path!
> >> And running pandoc with --verbose shows that the PATH is
> >> correctly passed through to the process running pdflatex.
> >>
> >> Anyone have any ideas? AT least this gives a workaround...
> >>
> >
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/c70c1da4-1ec9-4d34-aed3-7abf1c689adan%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/90890444-d6c0-43e3-a8be-9c005c750e4dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3926 bytes --]