Debugger variables displays TypeError when debugging async jest test function

[ibl-bkoenig]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.82.2
• OS Version: Windows 11

Steps to Reproduce:

1. Debug async jest function
2. VSCode reports the following error in the debug variables when attempting to read a class object

Error processing variables: TypeError: Cannot read properties of undefined (reading 'subtype') at new hC (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:11521) at Up.createVariable (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:3397) at Up.createVariableByType (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:3699) at Up.createPropertyVar (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:6444) at Up.createObjectPropertyVars (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:5471) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Fa.getVariables (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:114:16640) at async ml._onVariables (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:159:3583) at async Bl._onMessage (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\ms-vscode.js-debug\src\extension.js:71:4859)

In logs 'sharedprocess.log'

2023-09-26 17:44:22.638 [error] [uncaught exception in sharedProcess]: Cannot read properties of undefined (reading 'then'): TypeError: Cannot read properties of undefined (reading 'then')
at v.s (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:26:4731)
at v.q (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:26:4161)
at c.value (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:26:3566)
at b.w (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:21:1902)
at b.x (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:21:1972)
at b.fire (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:21:2188)
at MessagePortMain.te (c:\Users\Brett\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:19:40559)
at MessagePortMain.emit (node:events:513:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

[connor4312]

/jsDebugLogs

[vscodenpa]

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

[connor4312]

Thanks for the emailed log, fixed in the next nightly build