Open hogmuzzle opened 3 years ago
Try running with unsafe disabled, it gives a slight performance penalty. In the past stuff like this happened because of unintended multithreading which could cause ill-typed setField calls on unsafe. Without unsafe you'll get an exception which might help finde the root cause (multithreading related)
Am Do., 18. Feb. 2021 um 15:27 Uhr schrieb hogmuzzle < notifications@github.com>:
Unhandled exception at 0x0000000066241B5F (jvm.dll) in hs_err_pid8748.mdmp: 0xC0000005: Access violation reading location 0x0000000000340020
We have carried out stress-testing of our application where the library is used along with the Hazelcast IMDG. OS used: Windows Server 2012 and Redhat Server JVM used: oracle 8 version (on Win server) and openjdk 11 version (on Linux) After about 2 hours our application stops with a JVM crash. The error is always the same (Access violation reading location) but the place where this violation happens is random. When we switched to a standard java serialization the problem disappeared.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/RuedigerMoeller/fast-serialization/issues/310, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOQYDDZSDUEUZUNMZHES6LS7UPUBANCNFSM4X2MS2IQ .
Unhandled exception at 0x0000000066241B5F (jvm.dll) in hs_err_pid8748.mdmp: 0xC0000005: Access violation reading location 0x0000000000340020
We have carried out stress-testing of our application where the library is used along with the Hazelcast IMDG. OS used: Windows Server 2012 and Redhat Server JVM used: oracle 8 version (on Win server) and openjdk 11 version (on Linux) After about 2 hours our application stops with a JVM crash. The error is always the same (Access violation reading location) but the place where this violation happens is random. When we switched to a standard java serialization the problem disappeared.