[Bug 172] New: GC assertion failure with smaller/limited heap (running RCBroken)
[email protected] Thu, 23 Feb 2006 15:02:33 -0500
| Newsgroups | gmane.comp.java.vm.sablevm.bugs |
|---|---|
| Message-ID | <[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=172
Summary: GC assertion failure with smaller/limited heap (running
RCBroken)
Product: SableVM
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: default
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
To reproduce (I did it with current trunk):
0. Install SableVM with debugging features enabled.
1. svn co svn+ssh://svn.sablevm.org/gadek/locking-new/benchmarks/RCBroken
2. cd RCBroken && javac RCBroken.java
3. sablevm -Y -p sablevm.heap.size.min=100000 -p sablevm.heap.size.max=1600000
RCBroken
Every once in a while you should get something like:
sablevm: gc_copying.c:121: _svmf_copy_object: Assertion `((void *) obj) >=
env->vm->heap.start && ((void *) obj) < env->vm->heap.alloc' failed.
Aborted
You might need to experiment with different values of sablevm.heap.size.max
The basic idea is to set it small. The assertion should happen within the first
few seconds. If it doesn't - then it probably won't happen later, just stop the
benchmark (Ctrl+C) and try again.
I have not seen it happening when the size of heap is unlimited.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.