
For Spark
此页面有 中文 版本
当前正在浏览 English,可一键切换到你的偏好语言 中文。
Spark is a tool used to test game performance, identify performance bottlenecks and lag. You can use Spark when you encounter game stutters or high latency.
After version 0.5.3 (possibly?), spark has been removed from the gto package. (/gtocore spark is a legacy command and will not work if spark is not installed.)
Spark does not work properly on some kernels, for example Danger! MC mod causes crash: The culprit is actually this line of code……_哔哩哔哩_bilibili
used by Sparkasync-profiler is incompatible with some Linux kernels
The closest spark issues are these two:
#512 Crash using spark-1.10.53 (Forge) on Alpine 3.18 with openjdk21-jre-headless This is Forge + 1.20.1 + spark 1.10.53 + JDK 21 under which a direct native crash occurs. Although the reporter is using Alpine/aarch64, not your Debian/amd64, the nature is the same: both spark's native profiler crashes directly in the host environment.
#535 Spark 1.20.1 Forge-47.4.10 (spark version 1.10.53) incompatible with Java 25 This is Forge 1.20.1 + spark 1.10.53 + Java 25 incompatible, which matches the symptoms you encountered earlier.
Additionally, there are:
So we can confirm at least two points:
This is not an isolated, strange issue just affecting you spark 1.10.53 in 1.20.1, Forge, Linux, and different JDK combinations, there have been reports of profiler-related crashes or unavailability issues.
The issue you're facing isn't limited to just Java 25 You've already tested:
JDK 25 will crash
JDK 21 will still crash, so it now seems more like spark 1.10.53's native profiler is incompatible with your Linux container environment, not just a Java major version issue.
I also looked at the async-profiler upstream releases:
Here we can see some very relevant fix directions:
v4.2: Re-implement SafeAccess crash protection
v4.3: Harden crash protection in StackWalker
v4.3: Support compilation on modern JDKs
v4.3: Workaround for the kernel PERF_EVENT_IOC_REFRESH bug
v4.3: Fix races related to VM termination