You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Matei Zaharia (JIRA)" <ji...@apache.org> on 2008/07/01 23:58:45 UTC
[jira] Commented: (HADOOP-3644) TestLocalJobControl test gets
OutOfMemoryError on 64-bit Java
[ https://issues.apache.org/jira/browse/HADOOP-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609723#action_12609723 ]
Matei Zaharia commented on HADOOP-3644:
---------------------------------------
Owen - that sounds good, though it might lead to a bit of confusion as more people start working with 64-bit Java.
> TestLocalJobControl test gets OutOfMemoryError on 64-bit Java
> -------------------------------------------------------------
>
> Key: HADOOP-3644
> URL: https://issues.apache.org/jira/browse/HADOOP-3644
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Matei Zaharia
> Priority: Trivial
> Fix For: 0.17.1, 0.18.0, 0.19.0
>
> Attachments: testmem.patch
>
>
> The TestLocalJobControl unit test fails on 64-bit Java on Linux with an OutOfMemoryError. Here is the exact Java environment:
> $ java -version
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_07-b03, mixed mode)
> The test runs fine with 32-bit Java. The problem is likely that some of the data structures become bigger when using 64-bit pointers. As a fix, I've suggested simply increasing the memory available to JUnit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.