Bug 824776 – SIGSEGV when heap set > 128GB

Bug 824776 - SIGSEGV when heap set > 128GB

Summary:	SIGSEGV when heap set > 128GB

Status:	NEW

Aliases:	None

Product:	JBoss Enterprise Application Platform 4
Classification:	JBoss
Component:	jbossas (Show other bugs)
Sub Component:
Version:	4.2.0
Hardware:	x86_64 Linux

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Fernando Nasser
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-05-24 04:57 EDT by Robin Bowes
Modified:	2012-05-24 04:57 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Trace from SIGSEGV crash (14.78 KB, application/octet-stream) 2012-05-24 04:57 EDT, Robin Bowes	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Robin Bowes 2012-05-24 04:57:33 EDT

Created attachment 586583 [details]
Trace from SIGSEGV crash

We get a SIGSEGV fault on jbossas start-up if -Xms/-Xmx are set bigger than about 128GB. It fails when set to 132000m.

This is jbossas-4.2.3-24.jpp5 / java-1.6.0-openjdk-1.6.0.0-1.22.1.9.8.el5_6 on RHEL 5.6

How reproducible:
Set -Xms132000m -Xmx132000m and start jbossas.

Steps to Reproduce:
1. Set heap size to 132000m (as described above)
2. Start jbossas
  
Actual results:
jbossas crashes with a SIGSEGV

Expected results:
jbossas starts normally

Additional info:
See attached trace.

Note You need to log in before you can comment on or make changes to this bug.