copy / copy/v86

Uncaught RangeError: Maximum call stack size exceeded

Open
#393 7 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
23.5k
Forks
1.9k
Avg merge
2d 14h
Merged PRs (30d)
7

Description

When booting Windows 8.1 with patched ntoskrnl/winload, or with PAE/NX bits enabled in the CPUID, the system halts and I get this error.
But it works just fine in QEMU:
`qemu-system-x86_64 -hda 8.1.img -m 1G -M accel=hvf --cpu host,-pae,-nx`

![image](https://user-images.githubusercontent.com/27508072/105068452-3f0c8c00-5a81-11eb-879c-7b6ced0b926f.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Windows 8.1 boot with patched ntoskrnl/winload or with PAE/NX enabled, using the reported QEMU command as the comparison case. Use the displayed RangeError and call stack to locate the failing emulator path; done means the system no longer halts under the reported configuration while the existing QEMU comparison remains useful.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.