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.

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

Running MiKTeX commands in parallel fails #222

Closed
3 tasks done
Sharken03 opened this issue Nov 20, 2018 · 1 comment
Closed
3 tasks done

Running MiKTeX commands in parallel fails #222

Sharken03 opened this issue Nov 20, 2018 · 1 comment
Assignees
Milestone

Comments

@Sharken03
Copy link

Checklist:

  • I am reporting a bug others will be able to reproduce
  • I have installed the latest MiKTeX updates
  • I have checked the MiKTeX log files

Step-by-step reproduction instructions
On a Windows machine do the following:
Create a minimal temp.tex file.
Install DbgView and start DbgView.
Set trace flags like this: setx MIKTEX_TRACE "access,core,mmap"
Run texify.exe:
texify.exe --batch --pdf --tex-option=-halt-on-error temp.tex

DbgView will now show something like this:
dbgviewoutput

Running multiple instances of Texify.exe will eventually lead to an access denied error like this:
Errorlog.txt

The root cause seem to be that MiKTeX by default writes to a common file, and having more than one instance of Texify.exe doing this will lead to an error.

A workaround is to mark the Data folder as read-only, which the code in winMemoryMappedFile.cpp will respect.
It would be a lot better if the design was changed, so that multiple instances of MiKTeX commands can be run.

@edocevoli
Copy link
Member

I think this is has been fixed with one the latest updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants