public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Jason Davies" <ophiochos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: errors converting docx files
Date: Thu, 06 May 2021 17:49:02 +0100	[thread overview]
Message-ID: <274588F4-8776-42E2-A982-3B8FAA3472C2@gmail.com> (raw)

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


             reply	other threads:[~2021-05-06 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 16:49 Jason Davies [this message]
     [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
     [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=274588F4-8776-42E2-A982-3B8FAA3472C2@gmail.com \
    --to=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).