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

ArrayIndexOutOfBoundsException crash on Hypixel Skyblock #594

Closed
Leo40Git opened this issue Mar 19, 2021 · 5 comments
Closed

ArrayIndexOutOfBoundsException crash on Hypixel Skyblock #594

Leo40Git opened this issue Mar 19, 2021 · 5 comments
Labels
E-duplicate Closed: Duplicate issue T-crash Type: Crash or hang

Comments

@Leo40Git
Copy link
Contributor

This issue was encountered while using a development build of Sodium!

Build is from commit 07c4cc1.

Reproduction Steps

I triggered this crash in an area that's locked behind a skill level, so you'll need to play some Skyblock before you can replicate it. Sorry!

  1. In Hypixel Skyblock, go to the Deep Caverns area
  2. Get to one of the lower levels - I replicated the crash in Slimehill and initially encountered it in Obsidian Sanctuary
  3. Wait - I'm unsure of what actually triggers the crash, but it seems to happen around these areas
  4. The game crashes

Crash Report File

Over here!

@Leo40Git Leo40Git added the T-crash Type: Crash or hang label Mar 19, 2021
@DragonEggBedrockBreaking

If you go below y=0, then this is a duplicate of #587

Can you reproduce with #589

You can download a build for that here:
https://github.com/CaffeineMC/sodium-fabric/actions/runs/660817686

@Leo40Git
Copy link
Contributor Author

You can't go below Y=0 here, bar falling off the map (and the exception details don't line up with that case: the AIOOB is caused by trying to reference the 16th element in a 16-length array, while falling below Y=0 tries to access the element at index -1).

Will now try with that PR.

@Leo40Git
Copy link
Contributor Author

Seems to be fixed by #589, so maybe this is a variant of #587 rather than a duplicate?

@DragonEggBedrockBreaking

Seems to be fixed by #589, so maybe this is a variant of #587 rather than a duplicate?

Then maybe you should post your log and scenario on #587 and close this, since they are both fixed by the same PR?

@Leo40Git
Copy link
Contributor Author

Done.

@LucilleTea LucilleTea added the E-duplicate Closed: Duplicate issue label Jun 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-duplicate Closed: Duplicate issue T-crash Type: Crash or hang
Projects
None yet
Development

No branches or pull requests

3 participants