public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Allan Kelly <allankellynet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: errors converting to PDF ["can't allocate region"]
Date: Fri, 23 Jul 2021 07:53:16 -0700 (PDT)	[thread overview]
Message-ID: <c6639d65-1825-47b2-861e-f946d55aaf9en@googlegroups.com> (raw)
In-Reply-To: <m2eedb9hcp.fsf-jF64zX8BO0+iXxlc9qkzFr9bIa4KchGshsV+eolpW18@public.gmane.org>


[-- 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 --]

  parent reply	other threads:[~2021-07-23 14:53 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   ` errors converting to PDF ["can't allocate region"] John MacFarlane
     [not found]     ` <m2eedb9hcp.fsf-jF64zX8BO0+iXxlc9qkzFr9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-07-23 14:53       ` Allan Kelly [this message]
     [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=c6639d65-1825-47b2-861e-f946d55aaf9en@googlegroups.com \
    --to=allankellynet-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).