You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Eduard Shangareev (JIRA)" <ji...@apache.org> on 2018/07/24 18:16:00 UTC
[jira] [Resolved] (IGNITE-8937) JVM Crash in C++ suites on
Windows/Java 8 (in PageIO)
[ https://issues.apache.org/jira/browse/IGNITE-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eduard Shangareev resolved IGNITE-8937.
---------------------------------------
Resolution: Won't Fix
It's already fixed: no any JVM Crash for long time.
> JVM Crash in C++ suites on Windows/Java 8 (in PageIO)
> -----------------------------------------------------
>
> Key: IGNITE-8937
> URL: https://issues.apache.org/jira/browse/IGNITE-8937
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Ilya Kasnacheev
> Assignee: Eduard Shangareev
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCWindowsX64
> Builds of Platform C++ (Windows x64) and Platform C++ (Windows x86) fail almost every time with JVM Crash:
> {code}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x02537c64, pid=44768, tid=0x000056c8
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12)
> # Java VM: Java HotSpot(TM) Server VM (25.161-b12 mixed mode windows-x86 )
> # Problematic frame:
> # J 2991 C2 org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.initNewPage(JJI)V (48 bytes) @ 0x02537c64 [0x02537c40+0x24]
> {code}
> Looks like incorrect usage of Unsafe.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)