• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 646 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 280011
Options

Visual Studio Code Extension crashes Eletron on macOS

user106884

I'm running nRF Connect Extension Pack on macOS within VS Code

Whenever a Build or Pristine Build  has finished the terminal shows this message:


Terminal will be reused by tasks, press any key to close it.

when hitting Enter or any other key, the whole window manager is crashing du to an error in Electron.

Even remote connections like ssh will be closed, so it is not possible to fetch more logs.

Visual Studio

Version: 1.62.3
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T07:59:13.865Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.1.0

  • 0

    Hi,

    Thanks for reporting. I have not been able to reproduce this on my side, but I have forwarded the crash reports to the team. We do not have any explanation or suggested fix/workaroundat the moment, though.

  • 0

    I am seeing the same thing.

    I am on macOS Monterey with a 2018 Macbook Pro.

    I see it when I close VS Code as well, crashes all open programs.


    ------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Electron [84042]
Path:                  /Applications/Visual Studio Code.app/Contents/MacOS/Electron
Identifier:            com.microsoft.VSCode
Version:               1.62.3 (1.62.3)
Code Type:             X86-64 (Native)
Parent Process:        Exited process [10216]
User ID:               1700051200

Date/Time:             2021-12-01 15:26:58.3558 -0800
OS Version:            macOS 12.0.1 (21A559)
Report Version:        12
Bridge OS Version:     6.0 (19P549)
Anonymous UUID:        BEFA920E-F6A5-A235-B7DE-D6EAA324F1C0

Sleep/Wake UUID:       39BD80A8-FF1C-4BBF-9807-CE1070BCA24F

Time Awake Since Boot: 270000 seconds
Time Since Wake:       24298 seconds

System Integrity Protection: enabled

Notes:
dyld_process_snapshot_get_shared_cache failed

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00007ff81c44c5f3
Exception Codes:       0x0000000000000001, 0x00007ff81c44c5f3
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [84042]

VM Region Info: 0x7ff81c44c5f3 is not in any region.  Bytes after previous region: 140381302654452  Bytes before following region: 33883372045
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      Memory Tag 255             4b0a8c0000-4b0a974000   [  720K] rw-/rwx SM=PRV  
--->  GAP OF 0x7fb4f548c000 BYTES
      VM_ALLOCATE              7fffffe00000-7fffffe01000 [    4K] r--/r-- SM=ALI

  • 0 in reply to user18155

    Hi,

    I have forwarded it to our nRF Connect for VS Code team.

    We have not been able to reproduce it though, and from the logs it seems that the segfault is in Electron, which is far further down than the nRF Connect extensions. It could be that something the extension does trigger a VS Code or electron bug but we have not been able to pinpoint anything or see any reported VS Code issues that seem relevant.

Related
Terms of service