Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

large arrays show up as <null> in Godot debugger #76124

Closed
Spycemyster opened this issue Apr 16, 2023 · 2 comments
Closed

large arrays show up as <null> in Godot debugger #76124

Spycemyster opened this issue Apr 16, 2023 · 2 comments

Comments

@Spycemyster
Copy link
Contributor

Godot version

4.0.2.stable

System information

Windows 11, GLES2

Issue description

When there is a sufficiently large array, the Godot debugger will display it as <null>. It should probably be displayed as "too large to display" or anything other than null as that can be confusing.
image
I first discovered this when downloading images through an HTTPRequest. I was trying to find out why my image was displaying incorrectly, but the debugger kept showing <null> and made me incorrectly think that there was an issue with the request.

Steps to reproduce

Create an array and fill it with a large amount of elements. In the MVP I just kept doubling an array. After 17 times (131072 elements), that's when it started getting displayed as <null>.

Minimal reproduction project

LargeArrayMVP.zip

@Spycemyster
Copy link
Contributor Author

Also, if this is something that should be changed, I would like to take this issue on as my first issue.

@Calinou
Copy link
Member

Calinou commented Apr 16, 2023

Also, if this is something that should be changed, I would like to take this issue on as my first issue.

There's a pull request working around the issue: #74148

As per the PR's description, it's difficult to create a definitive fix that does not introduce network stalling due to data being too large. There's an attempt to improve the large data situation in #74230, but it needs to be reworked not to break compatibility.

@Calinou Calinou closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants