processing / processing/p5.js-web-editor

Incorrect Asset Size Limit Error

Open
#4,085 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Ready for Work
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

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:
Image

Screenshot of the total asset size:
Image

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the asset upload flow and reproduce the failure with a small font file while checking the displayed total asset usage against the 250 MB limit. Trace where the upload limit and current usage are calculated, then verify that an upload below the limit succeeds and that the error appears only when the limit is exceeded.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.