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

Error "Maximum call size exceeded" keeps on popping up when trying to code in a sprite #753

Open
n-d-v opened this issue Aug 10, 2023 · 3 comments

Comments

@n-d-v
Copy link

n-d-v commented Aug 10, 2023

I was just working on my big project, and i backpacked my own custom hashing algorithm to use in the big project, but when i first tried to import it, it did not show, no matter what i did. so, i tried to delete the item in the backpack and re-backpack the sprite, and then it worked, in which i just assumed that turbowarp just had a bit of trouble loading the sprite.
but after around 20 minutes of working on my project, the block count was abnormally large, as i had imported a sprite with roughly 300 blocks into a project with roughly 900 - 800 blocks, which should have made me have 1,300 blocks MAX, but the block count jumped to ~1,400, and then when i tried to go onto the sprite which i had backpacked, it did not work and it only showed the code of the previous sprite that was clicked, but all of the other sprites worked fine, so i went onto the glitched sprite, went on costumes and then went onto the code area again, which should have "refreshed" the code, but instead of seeing the code which i worked on a lot, i saw this, and it appeared on every sprite
image
and trying to close it and open it again didnt fix it.
(by the way, i had backups of my project, in case if your wondering if i lost all my work)

EDIT: it turns out that all of the projects i try to open (even extremely small ones) show the same error.
I had to FULLY close turbowarp and then open it, and then the issue was fixed. thew!
Another edit: when i try to go onto the sprite that caused the glitch, it causes the glitch all over again...

@GarboMuffin
Copy link
Member

Hey there, sorry for the delay

Can you send one of the broken project files to me? Either post it here in a zip or [email protected]

@n-d-v
Copy link
Author

n-d-v commented Aug 22, 2023

Hey there, sorry for the delay

Can you send one of the broken project files to me? Either post it here in a zip or [email protected]

When I tried to import the backpacked item into a blank project, it didn't work, but after trying again and again, it actually worked for some peculiar reason, and that was only when i re-backpacked the sprite for the 2nd time, and the project where the bug originally occurred now worked fine when importing it, which is really strange, and the only reason I can come up with is that I got unlucky and the backpack data wasn't saved properly twice.
Either way, the bug stopped appearing, and i couldn't replicate it, but here's the zip file with the sprite that would glitch out when backpacking:
Hashing Algorithm Test.zip

@n-d-v
Copy link
Author

n-d-v commented Aug 22, 2023

(also the block count became a normal 1.1k when getting the sprite from the backpack instead of the 1.3 - 1.4k i was getting before)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants