Fatal Error on Garbage Collection (Pt. 2)
Alan Bateman
Alan.Bateman at oracle.com
Wed Jul 29 14:01:14 UTC 2020
On 04/07/2020 23:09, Archon Dev wrote:
> Hello again, I recently was able to create a program that consistently
> crashes with a SIGSEGV error which appears to be caused by the garbage
> collector.
>
> Although, unlike the first issue I submitted, this error's problematic
> frame is:
> # V [libjvm.so+0x49241a] void
> Continuation::stack_chunk_iterate_stack_bounded<VerifyCleanCardClosure>(oopDesc*,
> VerifyCleanCardClosure*, MemRegion)+0x5a
>
> where as the previous issue's is:
> # V [libjvm.so+0x65a906]
> DefNewGeneration::copy_to_survivor_space(oopDesc*)+0x36
>
> I do believe they are related. What I have changed is my VM options: (along
> with forcing quicker process speeds to try to speed up the fatal error
> occurance)
> -XX:+UnlockDiagnosticVMOptions -XX:+VerifyBeforeGC -XX:+VerifyAfterGC
> -XX:+PrintGCDetails -XX:-OmitStackTraceInFastThrow -XX:NewSize=200m
> -XX:MaxNewSize=200m -XX:SurvivorRatio=8 -Xms512m -Xmx512m
>
> It is also important to note that I cannot get this fatal error to happen
> on a Windows OS, only Linux (Ubuntu)
>
> You can find the project along with more information in the README file at:
> https://github.com/NotArchon/Operation-Break-Loom
>
It's good to know you have a reproducer. Your README says "16-loom-2-14
(2020/6/27)". Do you know if it happens with the current EA build
(16-loom+3-56) ?
-Alan.
More information about the loom-dev
mailing list