starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal hangs when running yarn watch statement over a few days(even close or minimise doesn't work) #13767

New Issue
Closed
opened 2026-01-31 03:51:33 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 03:51:33 +00:00
Owner
Copy Link

Originally created by @brittotprince on GitHub (May 10, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

webpack-cli 3.3.12
yarn v1.22.4

Steps to reproduce

I have seen this issue multiple times when running yarn with a watch statement which inturn calls webpack

  • Run webpack builds that watch over the changes in a specified folder.
  • Leave it for over the weekend.

You can now see the whole 'terminal' is stuck. Not even close or minimize buttons work.

Expected Behavior

The terminal shouldn't hang when running for continuous builds

Actual Behavior

The terminal hangs after a couple of days. The top right buttons are also in the same state.

If we try to close 'Terminal' from the taskbar, the dialog box 'Do you want to close all tabs' comes up. But, it's not interactable and the clicks are not recorded.

The only way to close is to go to Task Manager and End the process.

Note: Verified that this issue is not happening for Command prompt.

Originally created by @brittotprince on GitHub (May 10, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software webpack-cli 3.3.12 yarn v1.22.4 ### Steps to reproduce I have seen this issue multiple times when running **yarn** with a watch statement which inturn calls webpack - Run webpack builds that watch over the changes in a specified folder. - Leave it for over the weekend. You can now see the whole 'terminal' is stuck. Not even close or minimize buttons work. ### Expected Behavior The terminal shouldn't hang when running for continuous builds ### Actual Behavior The terminal hangs after a couple of days. The top right buttons are also in the same state. If we try to close 'Terminal' from the taskbar, the dialog box 'Do you want to close all tabs' comes up. But, it's not interactable and the clicks are not recorded. The only way to close is to go to Task Manager and End the process. Note: Verified that this issue is not happening for Command prompt.
claunia commented 2026-01-31 03:51:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 13, 2021):

/feedback

@DHowett commented on GitHub (May 13, 2021): /feedback
claunia commented 2026-01-31 03:51:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 13, 2021):

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 (May 13, 2021): 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-31 03:51:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 13, 2021):

If you do end up with a Terminal instance in this state, can you use Task Manager to "Create [a] dump file..." of it (on the Details tab?) It's under WindowsTerminal.exe.

You can send that dump (please 7-zip it or something!) to me at the address on my GitHub profile.

@DHowett commented on GitHub (May 13, 2021): If you do end up with a Terminal instance in this state, can you use Task Manager to "Create [a] dump file..." of it (on the Details tab?) It's under `WindowsTerminal.exe`. You can send that dump (please 7-zip it or something!) to me at the address on my GitHub profile.
claunia commented 2026-01-31 03:51:36 +00:00
Author
Owner
Copy Link

@brittotprince commented on GitHub (May 16, 2021):

Hi, I will try to recreate this issue and do as instructed.

@brittotprince commented on GitHub (May 16, 2021): Hi, I will try to recreate this issue and do as instructed.
claunia commented 2026-01-31 03:51:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 21, 2021):

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 (May 21, 2021): 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**.
claunia commented 2026-01-31 03:51:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 21, 2021):

Oh, sorry about that! We may even be able to find crash reports if you file feedback now for the instance that occurred 11 days ago. 😄

@DHowett commented on GitHub (May 21, 2021): Oh, sorry about that! We may even be able to find crash reports if you file feedback _now_ for the instance that occurred 11 days ago. 😄
claunia commented 2026-01-31 03:51:37 +00:00
Author
Owner
Copy Link

@brittotprince commented on GitHub (May 21, 2021):

Hi,

Thank you for the message. I have shared the logs using the feedback hub just now. The title is the same as this thread and contains the issue number. Could you please check and let me know if something is missing.

Thankyou

@brittotprince commented on GitHub (May 21, 2021): Hi, Thank you for the message. I have shared the logs using the feedback hub just now. The title is the same as this thread and contains the issue number. Could you please check and let me know if something is missing. Thankyou
claunia commented 2026-01-31 03:51:37 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 21, 2021):

Sorry, we may need you to use the "Share a link to this feedback..." feature -- it turns out it is rather difficult to find an individual item in the feedback hub for us.

@DHowett commented on GitHub (May 21, 2021): Sorry, we may need you to use the "Share a link to this feedback..." feature -- it turns out it is rather difficult to find an individual item in the feedback hub for us.
claunia commented 2026-01-31 03:51:37 +00:00
Author
Owner
Copy Link

@brittotprince commented on GitHub (May 24, 2021):

Hi,

Attaching the feedback link

https://aka.ms/AAco62y

@brittotprince commented on GitHub (May 24, 2021): Hi, Attaching the feedback link https://aka.ms/AAco62y
claunia commented 2026-01-31 03:51:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 9, 2022):

Hey I dunno if we ever looked into this last year, but the feedback dump definitely timed out by now. Is this still happening/? If it is, filing feedback again might help debug. Otherwise, it might be easiest to do the following:

When the Terminal is frozen like this, could you grab a dump with Task Manager and send it to us?

image

That's more likely to get a stack of windowsterminal that'll actually show us what's deadlocked.

@zadjii-msft commented on GitHub (Sep 9, 2022): Hey I dunno if we ever looked into this last year, but the feedback dump definitely timed out by now. Is this still happening/? If it is, filing feedback again might help debug. Otherwise, it might be easiest to do the following: When the Terminal is frozen like this, could you grab a dump with Task Manager and send it to us? ![image](https://user-images.githubusercontent.com/18356694/135876584-e48514d6-26c0-49da-ae28-b8c5d66dc2a3.png) That's more likely to get a stack of windowsterminal that'll actually show us what's deadlocked.
claunia commented 2026-01-31 03:51:37 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 13, 2022):

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 (Sep 13, 2022): 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 Product-Terminal Severity-Crash
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#13767
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?