From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Jason Davies <ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: errors converting to PDF ["can't allocate region"]
Date: Wed, 09 Jun 2021 08:40:22 -0700 [thread overview]
Message-ID: <m2eedb9hcp.fsf@MacBook-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <274588F4-8776-42E2-A982-3B8FAA3472C2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
"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...
next prev parent reply other threads:[~2021-06-09 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 16:49 errors converting docx files Jason Davies
[not found] ` <274588F4-8776-42E2-A982-3B8FAA3472C2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-05-06 23:21 ` John MacFarlane
[not found] ` <m2fsyza1nx.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-05-07 17:34 ` BPJ
[not found] ` <CADAJKhARRDKJZea27J0_vxyMiB+57ASNQkiqkEeJBUjs1ztoDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-05-16 14:19 ` Philipp
[not found] ` <9d22d67f-fa8f-4989-84a6-344f7527e0fan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-28 19:57 ` Julio Vera
2021-06-09 15:40 ` John MacFarlane [this message]
[not found] ` <m2eedb9hcp.fsf-jF64zX8BO0+iXxlc9qkzFr9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-07-23 14:53 ` errors converting to PDF ["can't allocate region"] Allan Kelly
[not found] ` <c6639d65-1825-47b2-861e-f946d55aaf9en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-25 15:22 ` Lewis Westbury
[not found] ` <d58296d7-cc69-460c-8445-ca359c7f006fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-01 18:16 ` SlyFox
2021-08-01 18:19 ` SlyFox
[not found] ` <c70c1da4-1ec9-4d34-aed3-7abf1c689adan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-01 22:15 ` John MacFarlane
[not found] ` <m2k0l4olqh.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-08-02 8:31 ` SlyFox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2eedb9hcp.fsf@MacBook-Air.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).