starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

NPM install occasionally causing the terminal app to fault and close #4084

New Issue
Closed
opened 2026-01-30 23:37:37 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 23:37:37 +00:00
Owner
Copy Link

Originally created by @JCron245 on GitHub (Sep 26, 2019).

Environment

Windows build number: 10.0.18362.356
Windows Terminal version (if applicable): 0.4.2382.0

Node: 10.16.3 (via NVM and WSL)
NPM: 6.9.0

Steps to reproduce

  • Install Node using NVM in the WSL.
  • Using the BASH shell in terminal app from WSL (ubuntu).
  • Occasionally when running npm install the terminal will crash.

Expected behavior

NPM installs packages and the terminal remains usable.

Actual behavior

NPM begins installing packages and then the terminal closes.
No error message or crash feedback is generated, I do however see the error in my Event Viewer:

Log Name:      Application
Source:        Application Error
Date:          9/26/2019 1:10:52 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP.bs.local
Description:
Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.356, time stamp: 0x0825b5b0
Exception code: 0xc0000005
Fault offset: 0x00000000002ebcc3
Faulting process id: 0xa40
Faulting application start time: 0x01d5749cd2d18df8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 1017e52f-7257-4672-99eb-8ea615ef027e
Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-26T19:10:52.301063600Z" />
    <EventRecordID>5402</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP.bs.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WindowsTerminal.exe</Data>
    <Data>1.0.1908.26002</Data>
    <Data>5d641823</Data>
    <Data>Windows.UI.Xaml.dll</Data>
    <Data>10.0.18362.356</Data>
    <Data>0825b5b0</Data>
    <Data>c0000005</Data>
    <Data>00000000002ebcc3</Data>
    <Data>a40</Data>
    <Data>01d5749cd2d18df8</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data>
    <Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data>
    <Data>1017e52f-7257-4672-99eb-8ea615ef027e</Data>
    <Data>Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>
Originally created by @JCron245 on GitHub (Sep 26, 2019). # Environment ```none Windows build number: 10.0.18362.356 Windows Terminal version (if applicable): 0.4.2382.0 Node: 10.16.3 (via NVM and WSL) NPM: 6.9.0 ``` # Steps to reproduce - Install Node using NVM in the WSL. - Using the BASH shell in terminal app from WSL (ubuntu). - **_Occasionally_** when running `npm install` the terminal will crash. # Expected behavior NPM installs packages and the terminal remains usable. # Actual behavior NPM begins installing packages and then the terminal closes. No error message or crash feedback is generated, I do however see the error in my Event Viewer: ``` Log Name: Application Source: Application Error Date: 9/26/2019 1:10:52 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP.bs.local Description: Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.356, time stamp: 0x0825b5b0 Exception code: 0xc0000005 Fault offset: 0x00000000002ebcc3 Faulting process id: 0xa40 Faulting application start time: 0x01d5749cd2d18df8 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 1017e52f-7257-4672-99eb-8ea615ef027e Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-09-26T19:10:52.301063600Z" /> <EventRecordID>5402</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP.bs.local</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.0.1908.26002</Data> <Data>5d641823</Data> <Data>Windows.UI.Xaml.dll</Data> <Data>10.0.18362.356</Data> <Data>0825b5b0</Data> <Data>c0000005</Data> <Data>00000000002ebcc3</Data> <Data>a40</Data> <Data>01d5749cd2d18df8</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Windows\System32\Windows.UI.Xaml.dll</Data> <Data>1017e52f-7257-4672-99eb-8ea615ef027e</Data> <Data>Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 26, 2019):

/feedback

@DHowett-MSFT commented on GitHub (Sep 26, 2019): /feedback
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 26, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Sep 26, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@JCron245 commented on GitHub (Sep 26, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

Of course! --> https://aka.ms/AA65mja

@JCron245 commented on GitHub (Sep 26, 2019): > Hi there! > > Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end? > > Thanks! Of course! --> https://aka.ms/AA65mja
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Sep 26, 2019):

@JCron245, I cannot find a crash on the back end for your issue, sorry. Usually they come through off the feedback link.

Do you know how to capture the dump file yourself from the crashing application? It looks like this blog post has some instructions on how to tell WER to put the dumps in a location you can access them: https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/

@miniksa commented on GitHub (Sep 26, 2019): @JCron245, I cannot find a crash on the back end for your issue, sorry. Usually they come through off the feedback link. Do you know how to capture the dump file yourself from the crashing application? It looks like this blog post has some instructions on how to tell WER to put the dumps in a location you can access them: https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@JCron245 commented on GitHub (Sep 26, 2019):

@miniksa let me see if I can get a dump for you!

@JCron245 commented on GitHub (Sep 26, 2019): @miniksa let me see if I can get a dump for you!
claunia commented 2026-01-30 23:37:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 12, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Oct 12, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4084
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?