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

Possible system hang linked to a call to the ESENT API #8008

New Issue
Open
opened 2026-01-31 01:18:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:18:29 +00:00
Owner
Copy Link

Originally created by @Yevano on GitHub (May 8, 2020).

Feedback Hub link

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.778]
Windows Terminal version (if applicable): 0.11.1251.0

Steps to reproduce

Windows session had been alive for maybe a couple of weeks, and I'm sure the terminal had been open for several days between having the desktop in sleep mode. Reproducing this bug may be quite difficult, unless you happen to find the same error in the event viewer as I did. (below) Hopefully someone can filter for it to see if the problem is systematic, or if it is just my own system acting up.

Expected behavior

Obviously the program shouldn't just be allowed to hang a desktop due to a file access error, if that actually was the cause..

Actual behavior

I got an error message box, which I didn't have time to read since after a second or so all three of my monitors went black. After a hard reset, I had a look at the event viewer. I have sent logs to secure@microsoft.com as is stated that I should do in the template. The gist is that the call to ESENT causes an ERROR_NOT_FOUND exception while attempting to open the file C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

First time doing an issue here. If there is more info in the issue that I am supposed to share and I missed it, please let me know so that I can help with further investigation into this issue.

Originally created by @Yevano on GitHub (May 8, 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. --> [Feedback Hub link](https://aka.ms/AA8d0mj) # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.778] Windows Terminal version (if applicable): 0.11.1251.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Windows session had been alive for maybe a couple of weeks, and I'm sure the terminal had been open for several days between having the desktop in sleep mode. Reproducing this bug may be quite difficult, unless you happen to find the same error in the event viewer as I did. (below) Hopefully someone can filter for it to see if the problem is systematic, or if it is just my own system acting up. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Obviously the program shouldn't just be allowed to hang a desktop due to a file access error, if that actually was the cause.. # Actual behavior <!-- What's actually happening? --> I got an error message box, which I didn't have time to read since after a second or so all three of my monitors went black. After a hard reset, I had a look at the event viewer. I have sent logs to `secure@microsoft.com` as is stated that I should do in the template. The gist is that the call to ESENT causes an `ERROR_NOT_FOUND` exception while attempting to open the file `C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log`. First time doing an issue here. If there is more info in the issue that I am supposed to share and I missed it, please let me know so that I can help with further investigation into this issue.
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 Issue-Bug Needs-Tag-Fix Product-Terminal Resolution-No-Repro 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#8008
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?