processing / processing/processing4
loadFont("data/fontfile.vlw") crashes in executable but not in Processing (Mac)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
If one mistakenly calls loadFont("data/Avenir-Light-48.vlw"), instead of loadFont("Avenir-Light-48.vlw"), the call with "data":
- works in Processing
- crashes in an exported executable
This is Processing4.3, MacOS 15.4.1. Crashes on both x86 and aarch.
To test, create a font using Tools->Generate Font, then:
PFont font;
void setup() {
fullScreen(P2D);
frameRate(60);
font = loadFont("data/Avenir-Light-48.vlw");
}
void draw() {
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Processing 4.3 example on macOS, comparing the sketch in Processing with an exported executable on both architectures if available. Trace how loadFont resolves the data/font path in each environment. Done means the mistaken path no longer crashes the exported executable and its behavior is consistent with Processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100