[05:41] Hello! [05:42] I'm having what seems to be a Multipass-related issue on my desktop. Every once in a while (I would say 1~2 hours), my system becomes super slow. I cannot open new terminal windows, cannot switch to other programs, etc. [05:43] This morning I finally managed to start htop while this was happening, and I saw that `/snap/multipass/10053/bin/multipass.gui --autostarting` was using all of my CPU resources [05:44] At some point my desktop became completely unresponsive, so I went for lunch (thank you Multipass for reminding me it's lunchtime! :)) and when I came back, the system was responsive again. [05:45] I checked journalctl, and after 35 minutes, the system triggered oom-kill on a process, but I'm not sure if this is related to Multipass: [05:46] kernel: rpcbind invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 [05:46] (...) [05:46] kernel: Out of memory: Killed process 34036 (Isolated Web Co) total-vm:3918064kB, anon-rss:1178548kB, file-rss:0kB, shmem-rss:1724kB, UID:1000 pgtables:8680kB oom_score_adj:167 [05:47] I checked the Multipass logs with journalctl --unit 'snap.multipass*' but the last message there was from this morning: [05:47] multipassd[1313]: Checking for images to update… [05:48] And, importantly, all of that was triggered while I was doing absolutely nothing with Multipass :D I was browsing the Web and editing a file in Helix :D [05:48] Should I file a bug? If so, what logs would be helpful? [12:53] Hi pieq! Which driver are you using? Did this issue happen after you update Multipass? [15:03] luisp[m]: by driver, what do you mean? [15:03] luisp[m]: I didn't update Multipass. I have it installed because it's required by snapcraft (I need to build a few snaps from time to time) [16:08] pieq: sorry, I was referring to the backend Multipass is using. You can obtain it with `multipass get local.driver` [16:08] pieq: can you please tell which version of Multipass are you running? You can get it with `multipass version` [16:10] pieq: What I see in your logs is that the process being killed by the kernel has to do with the web browser. May I ask if this issue happens when you are _not_ using your web browser?