# VSCode hangs when opening or saving files **URL:** \ **Category:** Bluefin\ **Created:** [May 20, 2025, 8:27pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627 "2025-05-20T20:27:14Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 20, 2025, 8:27pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/1 "2025-05-20T20:27:14Z")
If I drop back to 41 GTS, will it have an older version of VSCode that might work for me? Doesn’t seem to matter the file system I am on, nor the folder I am in. The VSCode and VSCodium flatpaks have the same issue. Or, if there’s a fix, I’m all ears. Thanks ---
**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\ **Post date:** [May 20, 2025, 8:28pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/2 "2025-05-20T20:28:24Z")
vscode versions are the same across bluefins. Can you touch a file from within vscode? (is it permissions?) ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 20, 2025, 9:11pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/3 "2025-05-20T21:11:36Z")
I didn’t try touching a file from inside vscode. I discovered it hung up when I tried to open a file with ctrl-o. Very strange. I own all the files in my home. I created another user, same issue. I didn’t try disabling selinux. I did move my home to a separate, encrypted drive. Wouldn’t think that would matter. I’m installing 41 gts now out of desperation. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 20, 2025, 9:40pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/4 "2025-05-20T21:40:20Z")
I have a minimal system running on gts, and can get some work done. Then I’ll tread carefully with restoring my files, moving home, etc. ---
**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\ **Post date:** [May 20, 2025, 10:12pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/5 "2025-05-20T22:12:47Z")
Is this the same machine where the filesystem blew up randomly one day? Starting to suspect hardware if this is the case. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 20, 2025, 10:29pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/6 "2025-05-20T22:29:22Z")
I think that was in December, and I don’t recall what happened. The last few days’ troubles have been biological, as I think I hosed some settings when setting up the encrypted drives, resulting in failure to boot. After all the restoring, the thing with vscode is bizarre. Don’t see how I could have caused that, unless it was from restoring my home from a backup, and having to chown the files. Maybe selinux got mad. 🤷 Thanks for chiming in, I know you have many irons in many fires. ---
**Author:** ![x-0D](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/x-0d/32/6607_2.png) [@x-0D](https://universal-blue.discourse.group/u/x-0D)\ **Post date:** [May 21, 2025, 12:07pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/7 "2025-05-21T12:07:30Z")
Having just the same issue. Today vscode suddenly broke. Files and folders won’t open with ctrl-o or from context menu, causing vscode freeze. I can touch files within vscode. And i can open directories with ```shell code /path/to/dir ``` Also, there’s suddenly bazaar (`io.github.kolunmi.bazaar.desktop` at `/usr/share/applications`) appeared in gnome apps menu. I didn’t install it and seems it don’t work, only desktop file exists. At the same time chromium installed from flatpak stopped working with ERR\_NO\_SUPPORTED\_PROXIES error when opening websites. Are bluefin-dx images hacked or just broken? ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 12:19pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/8 "2025-05-21T12:19:16Z")
Same, and same. Chromium has been weird on mine too. Saying it doesn’t have network access. Phew. This looks bad. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 12:20pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/9 "2025-05-21T12:20:22Z")
Bazaar was recently added, it’s mentioned in one of Jorge’s announcements [here](https://universal-blue.discourse.group/t/call-for-testing-bazaar-as-a-flathub-store/8599). ---
**Author:** ![x-0D](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/x-0d/32/6607_2.png) [@x-0D](https://universal-blue.discourse.group/u/x-0D)\ **Post date:** [May 21, 2025, 12:24pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/10 "2025-05-21T12:24:25Z")
Found this issue about chromium problems. > > > appears after few minutes using browser > > Kubuntu 23.10 > Flatpak 1.14.4 > Linux …HONOR 6.5.0-21-lowlatency #21.1-Ubuntu SMP PREEMPT\_DYNAMIC Mon Feb 12 18:35:36 UTC 2024 x86\_64 x86\_64 x86\_64 GNU/Linux But it seems nothing about vscode freezes when open files and folders on internet. Is there way to rollback to previous `bluefin-dx:stable` update? ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 12:26pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/11 "2025-05-21T12:26:44Z")
Unfortunately not, only reinstalling. 42 switched to composefs, so there is no rolling back. I’m installing GTS, which is still on 41. ---
**Author:** ![x-0D](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/x-0d/32/6607_2.png) [@x-0D](https://universal-blue.discourse.group/u/x-0D)\ **Post date:** [May 21, 2025, 12:41pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/12 "2025-05-21T12:41:44Z")
rebased from stable to previous stable version (42-20250515) via ujust rebase-helper. vscode works well, broken bazaar desktop file is gone, and chromium… IDK, i switched to ungoogled-chromium already. Disabled automatic updates until vscode problem is not fixed ---
**Author:** ![mheuvel-dev](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/mheuvel-dev/32/5173_2.png) [@mheuvel-dev](https://universal-blue.discourse.group/u/mheuvel-dev)\ **Post date:** [May 21, 2025, 12:56pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/13 "2025-05-21T12:56:01Z")
Same problem with VS Code here, although I rarely use that open menu. When using the Ctrl-O menu for opening a file, VS Code freezes. I guess it is an upstream VS Code issue. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 1:07pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/14 "2025-05-21T13:07:46Z")
Yeah, I don’t use open either, just tried it to see if it was a “writing files” problem. When I get my system back up, I’ll file an issue. I checked, and didn’t see anything already filed. Or, if one of you wants to file, I’ll be glad to +1 it. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 1:14pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/15 "2025-05-21T13:14:48Z")
Was that 42.20250515.5? Or without the .5? ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 2:44pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/16 "2025-05-21T14:44:47Z")
Seriously? ```plaintext ❯ sudo zpool import [sudo] password for john: pool: tank id: 12697984504468729874 state: UNAVAIL status: The pool is formatted using an incompatible version. action: The pool cannot be imported. Access the pool on a system running newer software, or recreate the pool from backup. see: http://www.sun.com/msg/ZFS-8000-A5 config: tank UNAVAIL newer version raidz1-0 ONLINE disk/by-id/wwn-0x5000cca296c0f2d4-part1 ONLINE disk/by-id/ata-WDC_WD161KRYZ-01AGBB0_4BKPNTKH-part1 ONLINE disk/by-id/wwn-0x5000cca2cbc0ec45-part1 ONLINE disk/by-id/wwn-0x5000cca2cbc0e9c9-part1 ONLINE ``` ---
**Author:** ![x-0D](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/x-0d/32/6607_2.png) [@x-0D](https://universal-blue.discourse.group/u/x-0D)\ **Post date:** [May 21, 2025, 4:14pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/17 "2025-05-21T16:14:11Z")
Without .5 at the end. I selected it from the interactive menu ---
**Author:** ![mheuvel-dev](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/mheuvel-dev/32/5173_2.png) [@mheuvel-dev](https://universal-blue.discourse.group/u/mheuvel-dev)\ **Post date:** [May 21, 2025, 4:43pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/18 "2025-05-21T16:43:06Z")
Here you go: > > > Type: \Bug\ > > 1. Click \`File-\>Open...\` (Ctrl-O) or \`File-\>Save as...\` > 2. Clo…se the dialog (either open or save a file or cancel) > 3. The editor and all UI menues are frozen; only exiting VS Code may work. > > See other users reporting the same issue on Fedora 42 images: > https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/16 > > VS Code version: Code 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-14T21:47:40.416Z) > OS version: Linux x64 6.14.3-300.fc42.x86\_64 > Modes: > > \ > \System Info\ > > |Item|Value| > |---|---| > |CPUs|Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2693)| > |GPU Status|2d\_canvas: enabled\canvas\_oop\_rasterization: enabled\_on\direct\_rendering\_display\_compositor: disabled\_off\_ok\gpu\_compositing: enabled\multiple\_raster\_threads: enabled\_on\opengl: enabled\_on\rasterization: enabled\raw\_draw: disabled\_off\_ok\skia\_graphite: disabled\_off\video\_decode: enabled\video\_encode: disabled\_software\vulkan: disabled\_off\webgl: enabled\webgl2: enabled\webgpu: disabled\_off\webnn: disabled\_off| > |Load (avg)|2, 1, 1| > |Memory (System)|15.48GB (10.21GB free)| > |Process Argv|--disable-extensions --crash-reporter-id eeb7a480-f269-4c9d-a538-8f6d82b18c18| > |Screen Reader|no| > |VM|0%| > |DESKTOP\_SESSION|gnome| > |XDG\_CURRENT\_DESKTOP|GNOME| > |XDG\_SESSION\_DESKTOP|gnome| > |XDG\_SESSION\_TYPE|wayland| > \Extensions disabled\ > \A/B Experiments\ > > \`\`\` > vsliv368cf:30146710 > vspor879:30202332 > vspor708:30202333 > vspor363:30204092 > vscod805:30301674 > binariesv615:30325510 > c4g48928:30535728 > azure-dev\_surveyone:30548225 > 962ge761:30959799 > h48ei257:31000450 > pythontbext0:30879054 > cppperfnew:31000557 > dwnewjupyter:31046869 > pythonrstrctxt:31112756 > nativeloc1:31192215 > 5fd0e150:31155592 > dwcopilot:31170013 > 6074i472:31201624 > dwoutputs:31242946 > customenabled:31248079 > hdaa2157:31222309 > copilot\_t\_ci:31222730 > e5gg6876:31282496 > pythoneinst12:31285622 > bgtreat:31268568 > 4gafe986:31271826 > c7cif404:31309971 > 996jf627:31283433 > pythonrdcb7:31303018 > usemplatestapi:31297334 > 0aa6g176:31307128 > 7bj51361:31289155 > 747dc170:31275177 > pylancecolor:31309108 > aj953862:31281341 > generatesymbolt:31295002 > convertfstringf:31295003 > gendocf:31295004 > > \`\`\` > > \ It feels related to this issue in VS Code 3 years ago: > > > System: Red Hat Enterprise Linux Workstation release 7.9 (Maipo) > OS: Linux myh…ost 3.10.0-1160.36.2.el7.x86\_64 #1 SMP Thu Jul 8 02:53:40 UTC 2021 x86\_64 x86\_64 x86\_64 GNU/Linux > > This began as an occasional annoyance and has escalated into a 100% reproducible annoyance. > Using the latest snap install, during normal editing/debugging/etc. on local system. With increasing frequency, Ctrl-O/File-\>Open would completely freeze the UI with just a blinking cursor. Sometimes switching away and back would repaint part of the screen, increasingly not. Tried switching the output window to various things before attempting the file open (extension manager, main window, etc), but no output was observed before the freeze. > > Once the UI is frozen, only kill/killall seems to be able to get rid of it. Not sure if it means anything, but de-maximize and maximize still resize the window frame, although the contents aren't redrawn. Can't remember if that requires app cooperation or it that is a pure WM thing. > > Using snap installed code-insiders made no difference. > Uninstalling snap versions and downloading 1.65.0 from the MS repo so far seems to have restored functionality (1.66.0 requires a glibc version unavailable for RHEL7). > Haven't tried with (all) extensions disabled, but did disable everything I don't need constantly. > > One change in workflow recently seems suspiciously coordinated with the start of the issues - began using VS Code on another machine (nfs-mounted home folder, so shared settings/etc.) to attach to running containers (as container-specific user, to specific folder inside container), debug processes inside container, etc. > > Perhaps something got saved in the settings that is redirecting local File-\>Open to the remote-containers extension? Probably not, but the timing is mighty suspicious. ---
**Author:** ![JohnAtl](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/johnatl/32/3485_2.png) [@JohnAtl](https://universal-blue.discourse.group/u/JohnAtl)\ **Post date:** [May 21, 2025, 5:01pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/19 "2025-05-21T17:01:44Z")
Thanks! Don’t know if this is a vscode, Fedora, gnome, or Electron issue, but hopefully someone can sort it out. ---
**Author:** ![korbel](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/korbel/32/6491_2.png) [@korbel](https://universal-blue.discourse.group/u/korbel)\ **Post date:** [May 21, 2025, 5:24pm UTC](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627/20 "2025-05-21T17:24:25Z")
Checked the crash dump, looks like `xdg-desktop-portal` crashes which affects all file pickers of flatpak apps: ```auto Program terminated with signal SIGSEGV, Segmentation fault. #0 xdp_app_info_flatpak_new (pidfd=0x7f8b5b7fd43c, pid=, error=0x7f8b5b7fd450) at ../src/xdp-app-info-flatpak.c:829 829 app_info_flatpak->flatpak_info = g_steal_pointer (&metadata); ``` > > **backtrace** > > ```auto > Thread 1 (Thread 0x7f8b5b7fe6c0 (LWP 4701)): > #0 xdp_app_info_flatpak_new (pidfd=0x7f8b5b7fd43c, pid=, error=0x7f8b5b7fd450) at ../src/xdp-app-info-flatpak.c:829 > app_info_flatpak = 0x0 > flags = (XDP_APP_INFO_FLAG_HAS_NETWORK | XDP_APP_INFO_FLAG_SUPPORTS_OPATH | XDP_APP_INFO_FLAG_REQUIRE_GAPPINFO) > info_fd = 36 > stat_buf = {st_dev = 90, st_ino = 25, st_nlink = 1, st_mode = 33152, st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 2404, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1747846731, tv_nsec = 218513420}, st_mtim = {tv_sec = 1747846731, tv_nsec = 218513420}, st_ctim = {tv_sec = 1747846731, tv_nsec = 218513420},__ glibc_reserved = {0, 0, 0}} > local_error = 0x0 > mapped = 0x7f8b4c027400 > metadata = 0x0 > group = > id = 0x7f8b4c00c1a0 "org.gnome.NautilusPreviewer" > instance = 0x7f8b4c0118c0 "4026957808" > shared = 0x7f8b4c011900 > has_network = 1 > bwrap_pidfd = 37 > #1 xdp_connection_create_app_info_sync (cancellable=0x0, connection=0x56485e930320, sender=0x7f8b64000c50 ":1.137", error=0x7f8b5b7fd588) at ../src/xdp-app-info.c:972 > app_info = 0x0 > pidfd = 34 > pid = 5957 > local_error = 0x7f8b4c036100 > app_info_kind = 0x0 > __func__ = > #2 xdp_invocation_ensure_app_info_sync.constprop.0 (invocation=, error=0x7f8b5b7fd588, cancellable=0x0) at ../src/xdp-app-info.c:1084 > connection = 0x56485e930320 > sender = 0x7f8b64000c50 ":1.137" > app_info = 0x0 > #3 0x0000564839d03759 in authorize_callback (interface=, invocation=0x7f8b5c01abc0, user_data=) at ../src/xdg-desktop-portal.c:144 > app_info = 0x0 > error = 0x0 > #4 0x00007f8b7825b3a6 in _g_cclosure_marshal_BOOLEAN__OBJECT (closure=0x7f8b5c00e0a0, return_value=0x7f8b5b7fd770, param_values=0x7f8b5b7fd800, marshal_data=, invocation_hint=, n_param_values=) at ../gio/gmarshal-internal.c:102 > cc = > data1 = > data2 = > callback = 0x564839d03720 > v_return = > __func__ = > _g_boolean_var_10 = > _g_boolean_var_11 = > #5 0x00007f8b781bca5c in g_closure_invoke (closure=0x7f8b5c00e0a0, return_value=0x7f8b5b7fd770, n_param_values=2, param_values=0x7f8b5b7fd800, invocation_hint=0x7f8b5b7fd750) at ../gobject/gclosure.c:833 > marshal = 0x7f8b7825b440 <_g_cclosure_marshal_BOOLEAN__OBJECT> > marshal_data = 0x0 > in_marshal = > real_closure = 0x7f8b5c00e080 > __func__ = "g_closure_invoke" > #6 0x00007f8b781daaba in signal_emit_unlocked_R (node=node@entry=0x7f8b5b7fd910, detail=detail@entry=0, instance=instance@entry=0x56485e978240, emission_return=emission_return@entry=0x7f8b5b7fd990, instance_and_params=instance_and_params@entry=0x7f8b5b7fd800) at ../gobject/gsignal.c:3902 > tmp = > handler = 0x56485e97ccf0 > accumulator = > emission = {next = 0x0, instance = 0x56485e978240, ihint = {signal_id = 30, detail = 0, run_type = (G_SIGNAL_RUN_FIRST | G_SIGNAL_ACCUMULATOR_FIRST_RUN)}, state = EMISSION_RUN, chain_type = 4} > class_closure = > hlist = > handler_list = 0x56485e97ccf0 > return_accu = > accu = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}} > signal_id = > max_sequential_handler_number = > return_value_altered = > n_params = > EMIT_RESTART = > __func__ = > #7 0x00007f8b781dc2ac in signal_emit_valist_unlocked (instance=instance@entry=0x56485e978240, signal_id=signal_id@entry=30, detail=detail@entry=0, var_args=var_args@entry=0x7f8b5b7fda70) at ../gobject/gsignal.c:3547 > return_value = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}} > error = 0x0 > rtype = 20 > static_scope = 0 > instance_and_params = > param_values = > node = > i = > node_copy = > __func__ = "signal_emit_valist_unlocked" > #8 0x00007f8b781dcd58 in g_signal_emit_valist (instance=0x56485e978240, signal_id=30, detail=0, var_args=var_args@entry=0x7f8b5b7fda70) at ../gobject/gsignal.c:3277 > No locals. > #9 0x00007f8b781dce13 in g_signal_emit (instance=instance@entry=0x56485e978240, signal_id=, detail=detail@entry=0) at ../gobject/gsignal.c:3597 > var_args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 0x7f8b5b7fdb50, reg_save_area = 0x7f8b5b7fda90}} > #10 0x00007f8b7830cb36 in dispatch_in_thread_func (task=0x56485e957a60, source_object=, task_data=0x7f8b5c0182a0, cancellable=) at ../gio/gdbusinterfaceskeleton.c:529 > data = 0x7f8b5c0182a0 > interface = 0x56485e978240 > flags = G_DBUS_INTERFACE_SKELETON_FLAGS_HANDLE_METHOD_INVOCATIONS_IN_THREAD > object = 0x0 > authorized = 1 > #11 0x00007f8b7829478c in g_task_thread_pool_thread (thread_data=0x56485e957a60, pool_data=) at ../gio/gtask.c:1585 > task = 0x56485e957a60 > #12 0x00007f8b7845bac2 in g_thread_pool_thread_proxy (data=) at ../glib/gthreadpool.c:336 > task = 0x56485e957a60 > pool = 0x56485e93c9e0 > #13 0x00007f8b7845a8e2 in g_thread_proxy (data=0x7f8b60000d40) at ../glib/gthread.c:893 > thread = 0x7f8b60000d40 > __func__ = "g_thread_proxy" > #14 0x00007f8b77deb1d4 in start_thread (arg=) at pthread_create.c:448 > ret = > pd = > out = > unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140236512290496, -7326437986813289824, 140236512290496, 140236741966176, 0, 140236741966439, -7326437986855232864, -7326483353023358304}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} > not_first_call = > #15 0x00007f8b77e6dcec in __GI___ clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 > > ``` [Next page](https://universal-blue.discourse.group/t/vscode-hangs-when-opening-or-saving-files/8627.md?page=2)