-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Closed
Labels
BugA bug in TypeScriptA bug in TypeScriptFix AvailableA PR has been opened for this issueA PR has been opened for this issueSource: TelemetryThe issue relates to the telemetry in editorsThe issue relates to the telemetry in editorsVS Code PriorityCritical issues that VS Code needs fixed in the current TypeScript milestoneCritical issues that VS Code needs fixed in the current TypeScript milestone
Milestone
Description
This issue comes from crash dumps in telemetry. We've tried to de-duplicate issues on a best-effort basis, comparing the sequence of methods called and the command requested while ignoring line numbers.
TypeScript version prefix: 3.7.2
VSCode version: 1.40.0
Command requested: updateOpen
Hitting sessions: 999
Five line hash: 4d92d6402109da29bcae978b166e587c
Stack:
at ProjectService.applyChangesInOpenFiles (tsserver.js:138343:34)
at _a.<computed> (tsserver.js:139212:46)
at <anonymous> (tsserver.js:140870:88)
at Session.executeWithRequestId (tsserver.js:140861:28)
at Session.executeCommand (tsserver.js:140870:33)
at Session.onMessage (tsserver.js:140893:35)
at <anonymous> (tsserver.js:142208:27)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
at unknown (suppressed.js)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptFix AvailableA PR has been opened for this issueA PR has been opened for this issueSource: TelemetryThe issue relates to the telemetry in editorsThe issue relates to the telemetry in editorsVS Code PriorityCritical issues that VS Code needs fixed in the current TypeScript milestoneCritical issues that VS Code needs fixed in the current TypeScript milestone