Incorrect Asset Size Limit Error

[Qianqianye]

p5.js version

2.0.3

What is your operating system?

Mac OS

Web browser and version

chrome://146.0.7680.180

Actual Behavior

I tried to upload a small font file(50KB), but received an error indicating that I had exceeded the total asset size limit of 250MB, which blocks the upload. My current total asset size is approximately 68 MB, which is below the stated 250 MB limit. This suggests the limit may be miscalculated or not reflecting actual usage.

Screenshot of the error:

Screenshot of the total asset size:

Expected Behavior

The upload should succeed, as my total asset usage is below the 250 MB limit.

Steps to reproduce

1. Navigate to asset upload.
2. Attempt to upload a small file (e.g., font file).
3. Observe error message preventing upload.

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.

[raclim]

Thanks for flagging this!

@yugalkaushik would you be interested in investigating into this if you have the chance, since you have familiarity with the parts related to the asset limit? I can also take a look into this!

[yugalkaushik]

@raclim I’ll take a look at it

[yugalkaushik]

I tried reproducing the issue, but everything seems to be working as expected on my end. Could you share any additional details

preview-limit.mp4

[raclim]

Also following up with other suggestions that could be impacting this:

• the asset size was being miscalculated beforehand
• or the previously raised issue where some assets are not being fully deleted from user accounts despite deletion from the 'My Assets' tab. (Currently, there is progress towards asset cleanup but the bug still exists in the codebase)

[Nixxx19]

i think i figured out why this happens. the size check on upload is counting every file in s3 for the user, but "my assets" only shows the ones that are actually referenced in a project. so if there are leftover files in s3 from older projects or deletions, they still count against the limit even though you cannot see them.

that matches what @raclim said, the size is effectively miscalculated because of orphans, and the orphans exist because the delete flows don't fully clean up. deleting from my assets removes the s3 file but doesn't touch any db state, removing a file from a project does the opposite, and deleting a full project only cleans up newer s3 files.

that also explains why @yugalkaushik could not reproduce it, a fresh account would not have orphans yet. @Qianqianye probably has some from older deletions.

would love to take this on if it is available! thinking a two part fix, make the size match what the user actually sees, and make sure every delete path cleans up both sides. happy to split into two prs if that helps review.