![]() Need to do some more tests.Ĭommunication over websockets might also cause lua calls as that is how normal users could extend the server side to add new functions. That may take in total more time but each collection is tiny and still quick I guess. Not sure when it would decide to run, so for next release I have now forced a garbage collection after every call. I could debug my memory increase and it is a result of the lua interpreter having not run garbage collector. So after 15 hours it increased to 45MB memory usage. If websocket is the problem, can you tell me how to use the api to send gcode to the printer. If repetier_ui is enable, the memory usage increase 4 hours after I use my code If repetier_ui is disable, the memory usage is stable But all connections have a timeout so that is not happening as fas as I can see. If it still stores missing data to send it would at some point use the memory. One thing I can think of is that one communication thread does not close when connection is closed (e.g. Do you have several printers connected? Would at least explain you are using 56MB RAM. Each connection adds one thread and each printer 2 more threads. My pi zero no external connections has 9. ![]() Also all threads use the same memory so it is not 15 * RES in your case. ![]() VIRST includes shared memory and shared libraries. RES or MEM% is what the software actively is using. The xinit line is starting xserver with chromium. Xinit -nocursor 2> /dev/null > /dev/null & Otherwise edit /home/pi/.bashrc at end you see The chromium browser is used for the touchscreen on your pi. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |