Excessive key presses caused Exception: System.InvalidOperationException: Cannot locate the offset in the rendered text that was pointed by the original cursor
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the exception path through RecomputeInitialCoords, ReallyRender, ForceRender, and Insert, using the reported key sequence and buffer dimensions as the investigation context. Determine a reproducible input or rendering state, then verify that equivalent excessive key presses complete without the InvalidOperationException.
Written by the indexing model from the issue text.
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues, especially the pinned issues.
Exception report
Oops, something went wrong.
Please report this bug with ALL the details below, including both the 'Environment' and 'Exception' sections.
Please report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new?template=Bug_Report.yaml
Thank you!
### Environment
PSReadLine: 2.4.5
PowerShell: 7.6.2
OS: Microsoft Windows 10.0.26200
BufferWidth: 110
BufferHeight: 27
Last 200 Keys:
l - A z M o d u l e Enter
c l e a r Enter
n p m Spacebar - g Spacebar o u t d a t e d Enter
n p m Spacebar i n s t a l l Spacebar - g Spacebar n p m @ 1 1 . 1 6 . 0 Enter
s RightArrow Enter
j n h s d 1 4 5 2 Spacebar Ctrl+Alt+@ Ctrl+Alt+? M Spacebar RightArrow Insert End m p l Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+o Ctrl+Spacebar Ctrl+m Insert DownArrow DownArrow DownArrow DownArrow DownArrow DownArrow n
### Exception
System.InvalidOperationException: Cannot locate the offset in the rendered text that was pointed by the original cursor. Initial Coord: (21, 27) Buffer: (120, 30) Cursor: (14, 29)
at Microsoft.PowerShell.PSConsoleReadLine.RecomputeInitialCoords(Boolean isTextBufferUnchanged)
at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender(RenderData renderData, String defaultColor)
at Microsoft.PowerShell.PSConsoleReadLine.ForceRender()
at Microsoft.PowerShell.PSConsoleReadLine.Insert(Char c)
at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey(PSKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken, Nullable`1 lastRunStatus)
Screenshot
My cat walked over my laptop keyboard and sat on it while looking at me innocently, asking for biscuits. After he moved away I saw this exception in my terminal. I asked him to try to reproduce it, but he was uncooperative.
https://github.com/user-attachments/assets/60a802c2-8db6-46cf-bd90-dbd7b7a871b5
Environment data
PS Version: 7.6.2
PS HostName: ConsoleHost (Windows Terminal)
PSReadLine Version: 2.4.5
PSReadLine EditMode: Windows
OS: 10.0.26100.1 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 30
Steps to reproduce
As it was my cat sitting on the keyboard that caused the crash, it's difficult to reproduce
Expected behavior
No exception
Actual behavior
The above exception occurs
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PSReadLine
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
PowerShell/PSReadLine#3470 · 3 reactions ·
All issues in PowerShell/PSReadLine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100