You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Gidaspov (Jira)" <ji...@apache.org> on 2021/07/01 09:15:00 UTC
[jira] [Updated] (IGNITE-14687) BinaryHeapOutputStream
BinaryOffheapOutputStream corrupt memory in case of overflow and cause JVM
crash
[ https://issues.apache.org/jira/browse/IGNITE-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Gidaspov updated IGNITE-14687:
-------------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required)
> BinaryHeapOutputStream BinaryOffheapOutputStream corrupt memory in case of overflow and cause JVM crash
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-14687
> URL: https://issues.apache.org/jira/browse/IGNITE-14687
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.10
> Reporter: Sergey Kosarev
> Assignee: Sergey Kosarev
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer is easy:
> while (true) out.writeByteArray(bytes);
> ----
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000002742b26, pid=17128, tid=0x00000000000024e4
> #
> ----
>
> Actually It happened to me occassionally when by mistake a compute job tried to return too many results. JVM crashed on the job result serialization.
> See link to full reproducers below.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)