I was having issue with memory and just found out that a number of processes were taking up a considerable amount of memory and they were all linked to django, but I don’t quite remember if I have ever installed it…
I tried to uninstall it but got the following warning message WARNING: Skipping django as it is not installed.
When I looked into the properties, the command lines were
python3 /home/diango/manage.py update_git_states
python3 /home/django/mangae.py rqworker -v 3 cleaning --worker-class cvat.rqworker.DefaultWorker
python3 /home/django/mangae.py rqworker -v 3 export --worker-class cvat.rqworker.DefaultWorker
python3 -m uvicorn --fd 0 --forwarded-allows-ips=* cvat.asgi:application
python3 -m uvicorn --fd 0 --forwarded-allows-ips=* cvat.asgi:application
python3 /home/django/rqscheduler.py --host cvat_redis --password -i 30 --path/home/django
Removing Django won’t stop the processes. You’ll need to stop them manually, likely however you started them.
It’s a little surprising that they’re still running. Depending on how you started them in the first place, clearly something happened to make it lose track of the processes.
I’m using python venv, and noticed that django was found in /home/venv/gym_venv/lib/python3.8/site-packages/sentry_sdk/integrations/django, when I ran find / -name django
The fact that you have it on your system does not explain why it’s running. It’s not something that is going to start itself simply because it’s installed.
What makes me think of either a conda or a docker container is the path identified in the commands:
Do you have a django directory in /home? If not, then there is some package being run in any number of ways to set up a virutal /home/django directory.
You can also try to chase this down by following the PID chain of these processes back up through their parent process to find what started them.
I’m also using a library called OSQP for a simulator called Gazebo in my local environment. And found following lines related to Django in .gitignore inside osqp directory
# Django stuff:
*.log
local_settings.py
But even if I commented it and even if I ended and killed the processes in System Monitor, they show up again…
I suggest you stop worrying about the files in your system, and chase this down by examining the processes involved. It’s going to be a lot more useful to find what is starting them and why.
In addition to chasing the PID chain, you can also check all the typical startup locations (“/etc/init”, systemd, etc). You might also want to look at any third-party packages, plugins, tools, widgets, etc that you have installed.
Your task manager just shows python3 processes. Which ones are related to your project? Are you sure it’s actually Django running (eg through uvicorn, as you mentioned above), or just say your editor’s integrations.
You mentioned the “properties” (not sure what they are) which are running uvicorn, which would run Django. Have you set those commands to be run by something?
And yes, after tracking PID, I found out that the consumption of memory was caused by CVAT. Aftter removing the corresponding dockers, the memory issue was solved.
