WT leaving DMP files but doesn't crash #18794

Closed
opened 2026-01-31 06:24:29 +00:00 by claunia · 10 comments
Owner

Originally created by @vefatica on GitHub (Nov 1, 2022).

Windows Terminal version

WindowsTerminal: Binary: 1.15.2210.14004, Store: 1.15.2874.0

Windows build number

Microsoft Windows 10 Pro for Workstations 10.0.19044.2130 (2009, 21H2)

Other Software

No response

Steps to reproduce

With this in settings.json,

  "profiles": 
    {
        "defaults": 
        {
        	"adjustIndistinguishableColors": "never",

WT (release) gives a "failed to load settings" message box and starts with the default settings (expected). But it also leaves one of these.

2022-10-31 23:40 336,676,561 WindowsTerminal.exe.6244.dmp

Expected Behavior

No dump file

Actual Behavior

See above.

Originally created by @vefatica on GitHub (Nov 1, 2022). ### Windows Terminal version WindowsTerminal: Binary: 1.15.2210.14004, Store: 1.15.2874.0 ### Windows build number Microsoft Windows 10 Pro for Workstations 10.0.19044.2130 (2009, 21H2) ### Other Software _No response_ ### Steps to reproduce With this in settings.json, ``` "profiles": { "defaults": { "adjustIndistinguishableColors": "never", ``` WT (release) gives a "failed to load settings" message box and starts with the default settings (expected). But it also leaves one of these. `2022-10-31 23:40 336,676,561 WindowsTerminal.exe.6244.dmp` ### Expected Behavior No dump file ### Actual Behavior See above.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:24:29 +00:00
Author
Owner

@vefatica commented on GitHub (Nov 1, 2022):

When I look closer, I see that it does crash (before it's shown) and it restarts itself.

@vefatica commented on GitHub (Nov 1, 2022): When I look closer, I see that it does crash (before it's shown) and it restarts itself.
Author
Owner

@zadjii-msft commented on GitHub (Nov 1, 2022):

Can you share the actual contents of the dmp with us? adjustIndistinguishableColors should default to never, so theoretically, that should no-op.

it does crash (before it's shown) and it restarts itself.

That's... real weird. Can you share your whole settings? Maybe it's trying to restore a saved session, and that session crashes/?

@zadjii-msft commented on GitHub (Nov 1, 2022): Can you share the actual contents of the dmp with us? `adjustIndistinguishableColors` _should_ default to `never`, so theoretically, that should no-op. > it does crash (before it's shown) and it restarts itself. That's... real weird. Can you share your whole settings? Maybe it's trying to restore a saved session, and that session crashes/?
Author
Owner

@vefatica commented on GitHub (Nov 1, 2022):

Here's the test I used. It looks like the first WT is the parent of the second one. Is there some sort of stub involved? Oddly, ProcessMonitor doesn't catch two instances.

v:\> start wt & & echo _STARTPID = %_startpid^n & pstat %_startpid /f IQBI+ & delay 1 & pstat *terminal* /f IQBI+

_STARTPID = 5640

PID:        5640
Path:       D:\wt\exe\wt.exe
Started:    2022-11-01 10:49:17.011355
PPID:       6056

PID:        11232
Path:       D:\wt\exe\WindowsTerminal.exe
Started:    2022-11-01 10:49:17.152414
PPID:       5640

The zipped dump file (with my settings) is too big to put here. Try this link

@vefatica commented on GitHub (Nov 1, 2022): Here's the test I used. It looks like the first WT is the parent of the second one. Is there some sort of stub involved? Oddly, ProcessMonitor doesn't catch two instances. ``` v:\> start wt & & echo _STARTPID = %_startpid^n & pstat %_startpid /f IQBI+ & delay 1 & pstat *terminal* /f IQBI+ _STARTPID = 5640 PID: 5640 Path: D:\wt\exe\wt.exe Started: 2022-11-01 10:49:17.011355 PPID: 6056 PID: 11232 Path: D:\wt\exe\WindowsTerminal.exe Started: 2022-11-01 10:49:17.152414 PPID: 5640 ``` The zipped dump file (with my settings) is too big to put here. Try this [link](https://1drv.ms/u/s!AnlY2Xl9fgjSgi8wrNnZRcJhJ_68?e=LSKsfK)
Author
Owner

@vefatica commented on GitHub (Nov 1, 2022):

P.S., I see two instances even when there's no crash (offending line removed from settings.json).

@vefatica commented on GitHub (Nov 1, 2022): P.S., I see two instances even when there's no crash (offending line removed from settings.json).
Author
Owner

@vefatica commented on GitHub (Nov 1, 2022):

OK, I didn't look carefully. The first process is actually WT.EXE, a stub. So the two instances arent really two instances Still there's a crash. It really does produce a crash dump and stay running!

@vefatica commented on GitHub (Nov 1, 2022): OK, I didn't look carefully. The first process is actually WT.EXE, a stub. So the two instances arent really two instances Still there's a crash. It really does produce a crash dump and stay running!
Author
Owner

@DHowett commented on GitHub (Nov 1, 2022):

Can you, per chance, share the dump? 😄

@DHowett commented on GitHub (Nov 1, 2022): Can you, per chance, share the dump? 😄
Author
Owner

@vefatica commented on GitHub (Nov 1, 2022):

Can you, per chance, share the dump?

I think I did that a couple hours ago. It was too big to put here; I gave a OneDrive link.

@vefatica commented on GitHub (Nov 1, 2022): > Can you, per chance, share the dump? I think I did that a couple hours ago. It was too big to put here; I gave a OneDrive link.
Author
Owner

@DHowett commented on GitHub (Nov 1, 2022):

Ah, I missed that. Thanks!

@DHowett commented on GitHub (Nov 1, 2022): Ah, I missed that. Thanks!
Author
Owner

@DHowett commented on GitHub (Nov 2, 2022):

Thanks again! This looks like the same thing as /dup #13955.

I know it doesn't seem like it, but there is an instance of Terminal exiting here. The call stack is in the same place: deconstructing the application while we exit the process. 😄

@DHowett commented on GitHub (Nov 2, 2022): Thanks again! This looks like the same thing as /dup #13955. I know it doesn't seem like it, but there _is_ an instance of Terminal exiting here. The call stack is in the same place: deconstructing the application while we exit the process. :smile:
Author
Owner

@ghost commented on GitHub (Nov 2, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 2, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18794