ifeelrobbed

Memory leak maybe? From /var/log/syslog: `Oct 16 12:28:53 pop-os kernel: [69600.171513] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-36.scope,task=python3.10,pid=48807,uid=1000 Oct 16 12:28:53 pop-os kernel: [69600.171634] Out of memory: Killed process 48807 (python3.10) total-vm:32734412kB, anon-rss:13482224kB, file-rss:65752kB, shmem-rss:14340kB, UID:1000...

Watching memory climb as I run it. Form restart to crash, with a little of the middle not in the screenshots.  

Unfortunately rebooting didn't seem to change anything.

> > Unfortunately rebooting didn't seem to change anything. > > Did you update Gradio and other stuff? Seems recent updates require new versions of libraries. `pip install pip-upgrader` and...

Dang. Got excited when I saw the commit [fix bug for latest model merge RAM improvement](https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/5c94aaf290f8ad7bf4499a91c268ad0791b0432f) However, I still maxed out memory, swap, and the process was killed after ~6...

Interesting. I'm using the following arguments: `--medvram --opt-split-attention --force-enable-xformers`

I just deactivated and deleted venv, reverted to 7d6042b908c064774ee10961309d396eabdc6c4a, which is the last commit before Gradio 3.5, commented out the line in webui.sh that performs `git pull` and let it...

Alright, after a day of no issues, I performed a git pull, modified requirements.txt and requirements_versions.txt back to gradio==3.4.1, and commented out the git pull line in webui.sh. So far...

Yeah, with my 2060 I have to use --medvram for it to work at all. The only way I've found to prevent the memory leak regardless of commit I revert...