Crash after 15 minutes of startup

Issue Type: Bug

With the snap build of vscode running on Ubuntu 21.04 (amd64), the vscode instance crashes after 15 minutes. The crash is reproducable and happens within a few seconds around the 15 minute mark.

The issue can be reproduced with --disable-extensions.

VS Code version: Code 1.60.2 (7f6ab5485bbc008386c4386d08766667e155244e, 2021-09-22T12:01:43.795Z) OS version: Linux x64 5.11.0-36-generic snap Restricted Mode: No

System Info

Item	Value
CPUs	Intel® Core™ i5-4200M CPU @ 2.50GHz (4 x 3100)
GPU Status	2d_canvas: unavailable_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: disabled_off rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: unavailable_software webgl2: unavailable_software
Load (avg)	0, 0, 0
Memory (System)	15.51GB (2.85GB free)
Process Argv	–no-sandbox --wait --crash-reporter-directory /tmp/crash --disable-extensions --waitMarkerFilePath /tmp/qoumv
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	wayland

Extensions disabled

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscorecescf:30358481
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
vsccppwtct:30364498
pythonvssor306:30344512
bridge0708:30335490
pygetstartedt2:30371810
dockerwalkthru:30370836
bridge0723:30353136
pythonrunftest32:30365366
pythonf5test824cf:30361778
javagetstartedc:30364665
pythonvspyt187cf:30365362
pydsgsc2:30361791

[ressu]

That’s a good find. I confirmed that this is indeed the case. Starting code with an empty $HOME gets rid of the problem. Copying ~/.pki to the empty home causes the crash to reappear. And of course deleting $HOME/.pki makes the issue go away again.

So I think we now know the root cause for certain.

[deepak1556]

Thanks for the logs, can confirm the library being loaded when accessing nssdb in your case very likely cofigured by the presence of the reader.

2512142 stat("/home/ressu/.pki/nssdb/cert9.db-journal", 0x7f8470a0dda0) = -1 ENOENT (No such file or directory)
2512142 stat("/home/ressu/.pki/nssdb/cert9.db-wal", 0x7f8470a0dda0) = -1 ENOENT (No such file or directory)
2512142 open("/usr/lib64/libcryptoki.so", O_RDONLY|O_CLOEXEC) = 111
2512142 open("/snap/code/115/usr/share/code/libpcsclite.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
2512142 open("/snap/code/115/usr/share/code/../../lib/x86_64-linux-gnu/libpcsclite.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
2512142 open("/snap/code/115/usr/share/code/../../../lib/x86_64-linux-gnu/libpcsclite.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
2512142 open("/snap/core/current/usr/lib/x86_64-linux-gnu/libpcsclite.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
2512142 open("/snap/core/current/lib/x86_64-linux-gnu/libpcsclite.so.1", O_RDONLY|O_CLOEXEC) = 111

Currently our snap base image is based on Ubuntu 16.04 which definitely contains an older version of the library that hits this bug https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830, this should be addressed once we update our snap core, refs https://github.com/microsoft/vscode/pull/127320. Please continue to use deb package till then.