Terminal crashes on Select Text -> Copy #8256

Closed
opened 2026-01-31 01:24:46 +00:00 by claunia · 9 comments
Owner

Originally created by @xobs on GitHub (May 19, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): Version: 0.11.1333.0

Steps to reproduce

  1. Select some text
  2. Right-click to copy

Expected behavior

Text is copied to the clipboard

Actual behavior

Occasionally the program closes, which I believe is a crash.

Additional Information

I checked the Microsoft Store, and I'm running the latest version. The Microsoft Store did not report that Terminal was updated.

The following application error appears in Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 0.11.2005.4001, time stamp: 0x5eb0c80f
Faulting module name: TerminalApp.dll, version: 0.11.2005.4001, time stamp: 0x5eb0c79c
Exception code: 0xc0000005
Fault offset: 0x000000000000a3f3
Faulting process id: 0x3dcc
Faulting application start time: 0x01d629a506f85949
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe\TerminalApp.dll
Report Id: 9447907e-b136-4532-874f-91a93dac2647
Faulting package full name: Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

This is a duplicate of https://github.com/microsoft/terminal/issues/5582 which is an issue that is now closed.

As a side note, why does the "Faulting package full name" list the version as "0.11.1251.0", when "About" shows the version as "0.11.1333.0"? I checked in the Microsoft Store and it didn't say an update was available, and I haven't installed any updates myself.

Originally created by @xobs on GitHub (May 19, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: `Microsoft Windows NT 10.0.18362.0` Windows Terminal version (if applicable): `Version: 0.11.1333.0` # Steps to reproduce 1. Select some text 2. Right-click to copy # Expected behavior Text is copied to the clipboard # Actual behavior Occasionally the program closes, which I believe is a crash. # Additional Information I checked the Microsoft Store, and I'm running the latest version. The Microsoft Store did not report that Terminal was updated. The following application error appears in Event Viewer: ``` Faulting application name: WindowsTerminal.exe, version: 0.11.2005.4001, time stamp: 0x5eb0c80f Faulting module name: TerminalApp.dll, version: 0.11.2005.4001, time stamp: 0x5eb0c79c Exception code: 0xc0000005 Fault offset: 0x000000000000a3f3 Faulting process id: 0x3dcc Faulting application start time: 0x01d629a506f85949 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe\TerminalApp.dll Report Id: 9447907e-b136-4532-874f-91a93dac2647 Faulting package full name: Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` This is a duplicate of https://github.com/microsoft/terminal/issues/5582 which is an issue that is now closed. As a side note, why does the "Faulting package full name" list the version as "0.11.1251.0", when "About" shows the version as "0.11.1333.0"? I checked in the Microsoft Store and it didn't say an update was available, and I haven't installed any updates myself.
claunia added the Needs-Tag-FixResolution-No-ReproNeeds-Attention labels 2026-01-31 01:24:46 +00:00
Author
Owner

@DHowett commented on GitHub (May 19, 2020):

This one is really interesting. I actually think we might have fixed it in #5856, but for some reason you were still running 1251. I bet that's actually because you got the update but hadn't relaunched (and fortunately, the store didn't stop you!)...
Those binary versions do match up with 1251 and not 1333, so . . . ¯_(ツ)_/¯

@DHowett commented on GitHub (May 19, 2020): This one is really interesting. I actually think we might have fixed it in #5856, but for some reason you were still running 1251. I bet that's actually because you got the update but hadn't relaunched (and fortunately, the store didn't stop you!)... Those binary versions do match up with 1251 and not 1333, so . . . ¯\_(ツ)_/¯
Author
Owner

@DHowett commented on GitHub (May 19, 2020):

Are you, per chance, using copyOnSelect?

@DHowett commented on GitHub (May 19, 2020): Are you, per chance, using `copyOnSelect`?
Author
Owner

@xobs commented on GitHub (May 19, 2020):

No, I don't have that enabled. The only interesting setting I have changed is useAcrylic and the acrylicOpacity values.

@xobs commented on GitHub (May 19, 2020): No, I don't have that enabled. The only interesting setting I have changed is `useAcrylic` and the `acrylicOpacity` values.
Author
Owner

@DHowett commented on GitHub (May 19, 2020):

/feedback

@DHowett commented on GitHub (May 19, 2020): /feedback
Author
Owner

@ghost commented on GitHub (May 19, 2020):

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 19, 2020): 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)
Author
Owner

@xobs commented on GitHub (May 19, 2020):

How can I leave Feedback? If I select "Feedback" from the drop-down menu, it takes me to https://github.com/microsoft/Terminal/issues

The documentation at https://github.com/microsoft/terminal/blob/master/doc/user-docs/index.md doesn't include the word "Feedback" at all.

@xobs commented on GitHub (May 19, 2020): How can I leave Feedback? If I select "Feedback" from the drop-down menu, it takes me to https://github.com/microsoft/Terminal/issues The documentation at https://github.com/microsoft/terminal/blob/master/doc/user-docs/index.md doesn't include the word "Feedback" at all.
Author
Owner

@xobs commented on GitHub (May 19, 2020):

Feedback: https://aka.ms/AA8gr1e
Also, opened https://github.com/microsoft/terminal/issues/5985 on the Feedback bot.

@xobs commented on GitHub (May 19, 2020): Feedback: https://aka.ms/AA8gr1e Also, opened https://github.com/microsoft/terminal/issues/5985 on the Feedback bot.
Author
Owner

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

Thanks for picking up on the feedback bot issue. 😄

@DHowett commented on GitHub (May 21, 2020): Thanks for picking up on the feedback bot issue. :smile:
Author
Owner

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

So, looking at the crash reports for Terminal here it's getting attributed to the same failing function that #5856 fixed. If you end up on 1.0, can you validate whether it's still happening for you?

Thanks!

(Resolving for now, but I will reopen if you can repro it)

@DHowett commented on GitHub (May 21, 2020): So, looking at the crash reports for Terminal here it's getting attributed to the same failing function that #5856 fixed. If you end up on 1.0, can you validate whether it's still happening for you? Thanks! (Resolving for now, but I will reopen if you can repro it)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8256