Snap VSCode设备上没有剩余空间

Question

我已经安装了VSCode很长时间了。它以前曾像这样崩溃过，但我设法通过设置：

sudo sysctl fs.inotify.max_user_watches=524288

但现在它已经严重得多了。当我尝试使用code --verbose启动vscode时，我得到的是：

amir@amir-pc:~$ code --verbose
(process:20078): Gtk-WARNING **: 15:08:48.237: Locale not supported by C library.
    Using the fallback 'C' locale.
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
[20104:1010/150848.496732:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable.
[20104:1010/150848.496791:ERROR:gpu_info_collector.cc(68)] gl::GLContext::MakeCurrent() failed
[20104:1010/150848.496808:ERROR:gpu_info_collector.cc(185)] Could not create context for info collection.
[20104:1010/150848.496824:ERROR:gpu_init.cc(64)] gpu::CollectGraphicsInfo failed.
[20104:1010/150848.499694:WARNING:x11_util.cc(1430)] X error received: serial 199, error_code 2 (BadValue (integer parameter out of range for operation)), request_code 155, minor_code 24 (X_GLXCreateNewContext)
[20104:1010/150848.500364:WARNING:x11_util.cc(1430)] X error received: serial 200, error_code 170 (GLXBadContext), request_code 155, minor_code 5 (X_GLXMakeCurrent)
[20104:1010/150848.501840:WARNING:x11_util.cc(1430)] X error received: serial 200, error_code 170 (GLXBadContext), request_code 155, minor_code 26 (X_GLXMakeContextCurrent)
[20104:1010/150848.501987:ERROR:viz_main_impl.cc(170)] Exiting GPU process due to errors during initialization
[20104:1010/150848.503057:WARNING:x11_util.cc(1430)] X error received: serial 201, error_code 170 (GLXBadContext), request_code 155, minor_code 4 (X_GLXDestroyContext)
[20078:1010/150848.507698:WARNING:gpu_process_host.cc(1193)] The GPU process has crashed 1 time(s)
[main 2020-10-10T11:38:48.537Z] Error: listen ENOSPC: no space left on device /run/user/1000/snap.code/vscode-6ecfff7c-1.40.2-main.sock
    at Server.setupListenHandle [as _listen2] (net.js:1209:19)
    at listenInCluster (net.js:1274:12)
    at Server.listen (net.js:1373:5)
    at /snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:194:613
    at new Promise ()
    at Object.t.serve (/snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:194:550)
    at Object.doStartup (/snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:544:732)
    at /snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:543:220
    at h.invokeFunction (/snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:255:601)
    at Object.startup (/snap/code/21/usr/share/code/resources/app/out/vs/code/electron-main/main.js:543:56)
[main 2020-10-10T11:38:48.540Z] Lifecycle#kill()

起初，我认为通过清除/run/user/1000/的内容，事情会变得很好。但是在执行cd /run/user/1000/ ; rm -rf * (这在某种程度上是危险的)之后，操作系统的窗口管理器(它的Ubuntu，所以它的lightdm)崩溃了。通过重新启动它的服务，我成功地启动了它，并使它再次工作，但是VSCode仍然存在这个问题。我又犯了同样的错误。

这是df -h在我的系统上的输出：

amir@amir-pc:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            5.8G     0  5.8G   0% /dev
tmpfs           1.2G  2.1M  1.2G   1% /run
/dev/sda1        73G   45G   25G  65% /
tmpfs           5.8G  109M  5.7G   2% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           5.8G     0  5.8G   0% /sys/fs/cgroup
/dev/loop0      8.0M  8.0M     0 100% /snap/pulsemixer/23
/dev/loop1      256K  256K     0 100% /snap/gtk2-common-themes/5
/dev/loop2      154M  154M     0 100% /snap/chromium/958
/dev/loop3      150M  150M     0 100% /snap/gnome-3-28-1804/71
/dev/loop5       92M   92M     0 100% /snap/core/8592
/dev/loop7       88M   88M     0 100% /snap/go/4520
/dev/loop6      173M  173M     0 100% /snap/skype/100
/dev/loop8       34M   34M     0 100% /snap/pypy3/50
/dev/loop4      153M  153M     0 100% /snap/chromium/1026
/dev/loop9       32M   32M     0 100% /snap/pypy/30
/dev/loop10      90M   90M     0 100% /snap/core/8039
/dev/loop11      15M   15M     0 100% /snap/remmina/3223
/dev/loop12      72M   72M     0 100% /snap/software-boutique/31
/dev/loop16     128K  128K     0 100% /snap/software-boutique/39
/dev/loop14     203M  203M     0 100% /snap/vlc/1049
/dev/loop17      55M   55M     0 100% /snap/core18/1265
/dev/loop15     175M  175M     0 100% /snap/inkscape/5874
/dev/loop13     203M  203M     0 100% /snap/vlc/1397
/dev/loop19      34M   34M     0 100% /snap/pypy/40
/dev/loop18      16M   16M     0 100% /snap/ubuntu-mate-welcome/420
/dev/loop20      55M   55M     0 100% /snap/core18/1668
/dev/loop21     8.0M  8.0M     0 100% /snap/pulsemixer/250
/dev/loop22      32M   32M     0 100% /snap/pypy3/37
/dev/loop23      15M   15M     0 100% /snap/remmina/3810
/dev/loop24     256K  256K     0 100% /snap/gtk2-common-themes/9
/dev/loop25     137M  137M     0 100% /snap/code/21
/dev/loop26      45M   45M     0 100% /snap/gtk-common-themes/1353
/dev/loop28      16M   16M     0 100% /snap/ubuntu-mate-welcome/411
/dev/loop27     220M  220M     0 100% /snap/gimp/189
/dev/loop29      45M   45M     0 100% /snap/gtk-common-themes/1440
/dev/loop30     175M  175M     0 100% /snap/inkscape/4693
/dev/sda3       608G  557G   21G  97% /mnt/9c710070-854e-463f-80bf-b291852869ba
tmpfs           1.2G   76K  1.2G   1% /run/user/1000

基本上我已经让我的电脑运行了将近28天。我的意思是，我只是暂停并继续它(由于一些硬件问题，它需要努力启动，当它关闭，它不能重新启动，所以我暂停和恢复了很长时间)。我知道这听起来很有趣，但目前我没有动力去修理任何东西。

这28天的不停使用会不会引起这个问题？它会不会导致这么多垃圾文件被创建，并最终阻止其他进程在硬盘驱动器/ ram上拥有空间？

我的电脑内存几乎是免费的：

我不能断定拉姆已经没有空间了。

我知道如何抑制这个问题。重新启动我的笔记本电脑。但问题不是这样解决的。它的压制。

有人知道如何解决这个问题吗？铬(短铬)运行，电报运行，Libreoffice工作。但是VSCode和Mate桌面应用程序崩溃了。

另一个进程刚刚结束：(看来我的电脑正在自毁)。

谢谢你的帮助。我在使用Ubuntu伙伴18.04。

Answer 1

实际上，我的笔记本电脑的显卡出了问题，之后无法启动。

我把它送去修了，现在没事了。