Open mcnutty26 opened 8 years ago
The real issue is Java.
I thought that that was declared a feature at LAN.
We've had the conversation before about the difference (or not, as the case may be) between bugs and features.
The difference is when we have both bug and wontfix it's a feature.
Oh yeah we should probably try starting the server with -Xms8G or something. Might actually help. Or maybe someone who actually understands the JVM can suggest something.
Temporary workaround in 1cc208bab5e36713d6eb0186b03dfc756fe0eed9 Tested with files up to 1G, can increase the memory limit if it's still a problem. We should probably figure out the maximum file size it's reasonable to accept.
Very appropriate Java approach here, solve the problem with more memory!
EDIT: 1GB is a very acceptable compromise for now. If this gets fixed an appropriate max is probably 10GB, assuming files are deleted after they're played.
Cause: uploading a file larger than (possibly?) 256mb Result: exception and stack trace