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

BUG: "Failed to create array size 256x128x2", exit to desktop #475

Closed
meag opened this issue Jan 25, 2021 · 14 comments
Closed

BUG: "Failed to create array size 256x128x2", exit to desktop #475

meag opened this issue Jan 25, 2021 · 14 comments
Labels
blocks-release Needs to be fixed before next release is complete needs-feedback blocked waiting for info/feedback/test-case etc

Comments

@meag
Copy link
Contributor

meag commented Jan 25, 2021

ezQuake version:
3.6 alpha 5

OS/device including version:
i9-9900k, 64gb, RTX 2070 Super FTW3 Gaming.

Describe the bug
Failed to create array size 256x128x2
"Frequently crashes after game is complete and scores are shown once it resets the map"

To Reproduce
"Frequently crashes after game is complete and scores are shown once it resets the map."
"It doesn't always happen. I can play the map 4x in a row and it loads fine the first 3 then crashes the fourth. Sometimes it crashes the first try. Sometimes it crashes before the first map I play even loads. Even crashes sometimes when I try loading maps locally."

Screenshots
image

Reported by 5h4ddoW on discord
shaddow.zip

@meag
Copy link
Contributor Author

meag commented Jan 30, 2021

Looking into this - looks like the glGetError() is returning OUT_OF_MEMORY multiple times, so even when it reduces the size of the array, it keeps reporting a failure. Need to clear it out the errors before trying again but will see if there's obvious reason why it's happening first.

@meag
Copy link
Contributor Author

meag commented Feb 20, 2021

Am hoping this has improved with 63acd28

@meag meag added blocks-release Needs to be fixed before next release is complete needs-feedback blocked waiting for info/feedback/test-case etc labels Feb 20, 2021
@meag
Copy link
Contributor Author

meag commented Mar 12, 2021

Closing, will look at again if it is reported

@meag meag closed this as completed Mar 12, 2021
@dusty-qw
Copy link
Contributor

I'm still getting this error on about 50% of map changes... I believe it also happens occasionally during demo jumps.

@BLooD-DoG
Copy link
Contributor

I guess this should be reopened since it's still affecting Dusty and a couple other people trying to move to 3.6?

@meag meag reopened this Jul 7, 2021
@meag
Copy link
Contributor Author

meag commented Jul 7, 2021

@dusty-qw Can you:

  1. compile with WITH_RENDERING_TRACE defined
  2. run with -dev -r-trace
  3. change maps a few times until text files in qw/trace/ contains ERROR
  4. upload that zipped directory

please?

meag added a commit that referenced this issue Jul 12, 2021
Related to #475
This will get rid of the texture array failing
  due to errors in previous OpenGL calls
Would still like to debug further (-r-trace /
  -r-debug)
@meag
Copy link
Contributor Author

meag commented Jul 14, 2021

bump - @dusty-qw it would be good to do the -dev -r-trace thing to find where the OpenGL error was coming from
It should just be on map loads, but backwards demo_jumps would also be affected

@meag
Copy link
Contributor Author

meag commented Jul 18, 2021

bump - still looking for someone affected to

  • compile with WITH_RENDERING_TRACE defined
  • run with -dev -r-trace in command line
  • change maps a few times until text files in ./qw/trace/ contains ERROR
  • upload that zipped directory

@dusty-qw
Copy link
Contributor

Sure. I'm currently out of town, but I'll do it as soon I'm back (wednesday).

@meag
Copy link
Contributor Author

meag commented Jul 30, 2021

Hi @dusty-qw

Any chance of uploading some log files so I can try and debug this weekend?

Thanks,
meag

@dusty-qw
Copy link
Contributor

@meag I don't see any error messages in the logs. My client only seems to crash between matches, either when map reloads after score screen or after a vote map change. I can't seem to reproduce it by just joining a server and changing maps a bunch of times.

But I can still upload the logs if you think it's helpful.

@meag
Copy link
Contributor Author

meag commented Aug 1, 2021

Thanks @dusty-qw

If there definitely no errors in the logs, could you try again and maybe play a few 1-minute bot matches in a row and see if that will trigger it?

Is it still happening with latest source?

@meag
Copy link
Contributor Author

meag commented Aug 18, 2021

Hi @dusty-qw

Is this bug still happening for you in latest versions? I'll close it again for now if we can't reproduce.

Thanks,

@meag
Copy link
Contributor Author

meag commented Nov 6, 2021

Closing again due to lack of feedback

@meag meag closed this as completed Nov 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocks-release Needs to be fixed before next release is complete needs-feedback blocked waiting for info/feedback/test-case etc
Projects
None yet
Development

No branches or pull requests

3 participants