react-native-windows
react-native-windows copied to clipboard
Access violation writing location
Problem Description
We are seeing an issue in debug on larger fetch requests > 10mb (release is fine).
Issue was not present in prior version and also not present in android or ios.
Error being thrown is Access violation writing location at: WinRTHttpResource.cpp Line 398
We had an issue a few years back that had a hard cap at 10mb however that doesn't seem the be the issue this time.
Steps To Reproduce
Create a new project, fetch a data packet greater than 10mb.
Expected Results
Fetch succeeds
CLI version
11.3.10
Environment
OS: Windows 11 10.0.22621
CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13950HX
Memory: 39.33 GB / 63.65 GB
Binaries:
Node:
version: 18.17.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.19
path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm:
version: 9.6.7
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions:
- 10.0.18362.0
- 10.0.19041.0
- 10.0.22000.0
- 10.0.22621.0
IDEs:
Android Studio: Not Found
Visual Studio:
- 17.4.34302.79 (Visual Studio Professional 2022)
Languages:
Java:
version: 11.0.18
path: C:\Program Files\Microsoft\jdk-11.0.18.10-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.7
wanted: 0.72.7
react-native-windows:
installed: 0.72.20
wanted: 0.72.20
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Target Platform Version
10.0.19041
Target Device(s)
Desktop
Visual Studio Version
Visual Studio 2022
Build Configuration
Debug
Snack, code example, screenshot, or link to a repository
No response
@JunielKatarn Any immediate ideas?
Here's the relevant PR for the 10MB issue: https://github.com/microsoft/react-native-windows/pull/10885 But seems like you're hitting some problem with the new solution.
@chrisglein yeah, this is definitely different.
Only impacts dev this time so it's seems like it's a memory or space allocation capacity issue in dev whereas previously it was to do with the request size.