Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tectonic fail out of memory #122

Open
webbery opened this issue Jul 20, 2017 · 1 comment
Open

tectonic fail out of memory #122

webbery opened this issue Jul 20, 2017 · 1 comment

Comments

@webbery
Copy link

webbery commented Jul 20, 2017

Hi, I compiled a tex file in VirtualBox. Here is error info:

Running TeX ...
note: warnings were issued by the TeX engine; use --print and/or --keep-logs for details.
Running BibTeX ...
note: warnings were issued by BibTeX; use --print and/or --keep-logs for details.
Rerunning TeX because bibtex was run ...
Running xdvipdfmx ...
error: Out of memory - asked for 10663802 bytes

But tex file was build success after I closed atom editor. Does tectonic consume a lot of memory?
@pkgw
Copy link
Collaborator

pkgw commented Aug 28, 2017

Hmm, that is a very strange error. Tectonic uses preallocated memory arrays that are relatively large compared to a minimal TeX engine, but are extremely manageable for modern machines.

Are you able to produce a .tex file that consistently triggers this out of memory error, regardless of whether your editor is open or closed? I have trouble seeing how closing the editor would make the problem go away.

@Mrmaxmeier Mrmaxmeier mentioned this issue Oct 13, 2017
Merged
Mrmaxmeier pushed a commit to Mrmaxmeier/tectonic that referenced this issue Oct 4, 2019
@crlf0710
Merge pull request tectonic-typesetting#122 from Mrmaxmeier/oxidize
732be53 
dpx_pdfobj: fix NULL-deref introduced in `2958302`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pkgw @webbery