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

Crashing when trying to read address 0x0000000000000000 #15088

New Issue
Closed
opened 2026-01-31 04:28:15 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:28:15 +00:00
Owner
Copy Link

Originally created by @herkulessi on GitHub (Sep 4, 2021).

Windows Terminal version (or Windows build number)

Win32NT 10.0.19043.0 Microsoft Windows NT 10.0.19043.0

Other Software

No response

Steps to reproduce

  1. Wake up PC from Hibernation
  2. Quickly open Wintows Terminal twice (I used Win+1)

I could NOT reproduce this.

Expected Behavior

Two Windows Terminal windows opening.

Actual Behavior

One Terminal Window opened and I got the following Error message:
WinTerm Crash
Loose translation from german to English:
WindowsTerminal.exe - Error in Application
The instruction at 0x00007FF87423790E points to RAM at 0x0000000000000000. The action read couldn't be carried out in RAM.

Press "OK" to end the Application.

Originally created by @herkulessi on GitHub (Sep 4, 2021). ### Windows Terminal version (or Windows build number) Win32NT 10.0.19043.0 Microsoft Windows NT 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce 1. Wake up PC from Hibernation 2. Quickly open Wintows Terminal twice (I used Win+1) I could NOT reproduce this. ### Expected Behavior Two Windows Terminal windows opening. ### Actual Behavior One Terminal Window opened and I got the following Error message: <img width="299" alt="WinTerm Crash" src="https://user-images.githubusercontent.com/31536990/132104701-b6f58213-1741-410c-8909-d8ddfdb91bef.png"> Loose translation from german to English: WindowsTerminal.exe - Error in Application The instruction at 0x00007FF87423790E points to RAM at 0x0000000000000000. The action read couldn't be carried out in RAM. Press "OK" to end the Application.
claunia added the Needs-TriageNeeds-ReproProduct-Terminal labels 2026-01-31 04:28:15 +00:00
claunia commented 2026-01-31 04:28:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 14, 2021):

Weird. I've never seen this particular error dialog ever before. Looking around the web, it seems that this is something that can happen to any program, randomly. Also see this search. Might be that your RAM just got hit with a cosmic ray, or it's dying. I'm especially inclined to believe that hypothesis since

I could NOT reproduce this.

If you can get this to repro with any regularity, maybe we can reopen and see what what we find.

@zadjii-msft commented on GitHub (Sep 14, 2021): Weird. I've never seen this particular error dialog ever before. [Looking around the web](https://www.google.com/search?q=%22points+to+RAM+at+0x0000000000000000%22&oq=%22points+to+RAM+at+0x0000000000000000%22&aqs=edge..69i57.643j0j1&sourceid=chrome&ie=UTF-8), it seems that this is something that can happen to any program, randomly. Also see [this search]( https://www.google.com/search?q=%22Attempt+to+write+data+to+address%22&sxsrf=AOaemvK3eGdIEtP1zFM-DozoTz-FeQvlXA%3A1631639920360&ei=cNlAYYmsFYWF9PwPh-eksAw&oq=%22Attempt+to+write+data+to+address%22&gs_lcp=Cgdnd3Mtd2l6EAMyBggAEAUQHjoHCAAQRxCwA0oECEEYAFCEvhlYhL4ZYMrAGWgCcAJ4AIABlgGIAZYBkgEDMC4xmAEAoAECoAEByAEIwAEB&sclient=gws-wiz&ved=0ahUKEwiJpOqu_P7yAhWFAp0JHYczCcYQ4dUDCA4&uact=5). Might be that your RAM just got hit with a cosmic ray, or it's dying. I'm especially inclined to believe that hypothesis since > I could NOT reproduce this. If you can get this to repro with any regularity, maybe we can reopen and see what what we find.
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-Repro Needs-Triage Product-Terminal
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#15088
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?