IntellectualSites / IntellectualSites/FastAsyncWorldEdit
Relighting causing extreme memory/CPU usage
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 806
- Forks
- 394
- Avg merge
- 22h 19m
- Merged PRs (30d)
- 14
Description
Server Implementation
Spigot
Server Version
1.21.10
Describe the bug
Upon copy/pasting a lighting block (and perhaps also a lighting-affected block such as a block inside a lighting glitch?), the relighter draws huge memory usage, eventually leading to high CPU usage as garbage-collection struggles to keep up, and eventually a non-functioning server.
Relogging will in some instances cancel the relighting job, effectively fixing the bug, but also leaves large areas of broken lighting that can lead to further instances of the bug (it would seem). In at least one case, subsequently logging on and trying to use WorldEdit commands resulted in a job cancellation due to low memory, despite memory being available.
To Reproduce
- Start with blank server, just FAWE.
- Log in, place a glowstone block.
- //copy the glowstone block.
- Move to a new position, use //paste.
- Kaboom.
Expected behaviour
I expected the server to remain healthy ;)
Screenshots / Videos
https://xorg.us/idea64_2025-11-17_01-34-54.mp4
Error log (if applicable)
No response
Fawe Debugpaste
https://athion.net/ISPaster/paste/view/255ba270af8c4a90a7515c9527c2bda7
Fawe Version
FastAsyncWorldEdit version 2.14.1-SNAPSHOT-1214+6205e5c
Checklist
- I have included a Fawe debugpaste.
- I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.
Anything else?
No response
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
Start by reproducing the issue with a blank Spigot 1.21.10 server, FAWE, and the glowstone copy/paste steps. Inspect the linked FAWE debugpaste and observe the relighting job's memory and CPU behavior; done means the paste completes without runaway resource usage or leaving broken lighting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100