lots of luatex process/instances (ps xa| grep lua / top -----sort by memory)
Dear context users, at first a lot of warm thanks for help and comments on using t-simpleslides. On a different matter, I now have the following problem : I do a lot of testing trying compiling my slides (using the following command : "context essai.tex"). Sometimes, I get errors and an interactive prompt that I kill with either ctrl+C or ctrl+Z (at random). I noticed that my computer was swapping (2Go RAM). With "ps xa | grep lua" I get 34 process. Using "top" and sorting by memory used the processes, I noticed 7 instances of luatex and 5 of texlua on the first page for a total of 800MB of resident memory. Did I miss something using context (I do "context essai.tex" each time that I want compile changes) ? "killall luatex" and kill -15 PID does nothing. Best, Amaël
Sometimes, I get errors and an interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
You shouldn't do that. Type 'x' at the error prompt, it makes (Lua)TeX terminate. Ctrl+C sometimes isn't enough to kill LuaTeX, though I have no idea why; as for Ctrl+Z, it never kills anything, it sends the suspend signal (you should see the process status with top).
"killall luatex" and kill -15 PID does nothing.
kill -1 is usually enough. Arthur
Thank you ! it's ok now. Le dimanche 10 mai 2009 à 20:14 +0200, Arthur Reutenauer a écrit :
Sometimes, I get errors and an interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
You shouldn't do that. Type 'x' at the error prompt, it makes (Lua)TeX terminate. Ctrl+C sometimes isn't enough to kill LuaTeX, though I have no idea why; as for Ctrl+Z, it never kills anything, it sends the suspend signal (you should see the process status with top).
"killall luatex" and kill -15 PID does nothing.
kill -1 is usually enough.
Arthur ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
I've also noticed something along those lines. I've also found that CTRL+Z/C doesn't really exit the program --- there are stale processes still lying around. What I described is general, it tends to happen across big documents. Is this a known problem? � Broustet wrote:
Dear context users, at first a lot of warm thanks for help and comments on using t-simpleslides.
On a different matter, I now have the following problem : I do a lot of testing trying compiling my slides (using the following command : "context essai.tex"). Sometimes, I get errors and an interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
I noticed that my computer was swapping (2Go RAM). With "ps xa | grep lua" I get 34 process.
Using "top" and sorting by memory used the processes, I noticed 7 instances of luatex and 5 of texlua on the first page for a total of 800MB of resident memory.
Did I miss something using context (I do "context essai.tex" each time that I want compile changes) ?
"killall luatex" and kill -15 PID does nothing.
Best, Amaël
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
On a small example : ctrl+C works, ctrl+Z leaves unkillable (either -15 or -1) luatex and texlua process. kill -9 leaves zombies. killing the parent shell clean everything. Le dimanche 10 mai 2009 à 19:25 +0100, Mohamed Bana a écrit :
I've also noticed something along those lines. I've also found that CTRL+Z/C doesn't really exit the program --- there are stale processes still lying around.
What I described is general, it tends to happen across big documents.
Is this a known problem?
� Broustet wrote:
Dear context users, at first a lot of warm thanks for help and comments on using t-simpleslides.
On a different matter, I now have the following problem : I do a lot of testing trying compiling my slides (using the following command : "context essai.tex"). Sometimes, I get errors and an interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
I noticed that my computer was swapping (2Go RAM). With "ps xa | grep lua" I get 34 process.
Using "top" and sorting by memory used the processes, I noticed 7 instances of luatex and 5 of texlua on the first page for a total of 800MB of resident memory.
Did I miss something using context (I do "context essai.tex" each time that I want compile changes) ?
"killall luatex" and kill -15 PID does nothing.
Best, Amaël
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
On a small example : ctrl+C works, ctrl+Z leaves unkillable (either -15 or -1) luatex and texlua process.
Again, that's because Ctrl+Z, in a normal Unix environment, only suspends the process, it never kills it. Try kill -19 first (SIGCONT), then kill -15 or -1. You can try the following experiment: run a small example file with an error and type Ctrl+Z. You may think you exited the process, but now type "fg". You should recover the LuaTeX run in the exact state you left it. It has not been killed. Arthur
participants (4)
-
Amaël Broustet -
Arthur Reutenauer -
Martin Schröder -
Mohamed Bana