You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Rustem Rafikov (JIRA)" <ji...@apache.org> on 2007/12/03 08:54:43 UTC
[jira] Closed: (HARMONY-4274) [drlvm][gc_gen] jbb2005 crashes if
setting heap size >= 2G on linux 64 bit
[ https://issues.apache.org/jira/browse/HARMONY-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rustem Rafikov closed HARMONY-4274.
-----------------------------------
> [drlvm][gc_gen] jbb2005 crashes if setting heap size >= 2G on linux 64 bit
> --------------------------------------------------------------------------
>
> Key: HARMONY-4274
> URL: https://issues.apache.org/jira/browse/HARMONY-4274
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Machine: 3G woodcrest
> Linux: SUSE Linux Enterprise Server 10 (x86_64)
> Reporter: Rustem Rafikov
>
> DRLVM crashes with heap >=2G when running jbb2005.
> There are at leat 2 different stack traces:
> 1. The first one is frequently appeared when setting 2G exactly
> GC use large pages.
> SIGSEGV in VM code.
> Stack trace:
> 0: ?? (??:-1)
> 1: ?? (??:-1)
> 2: ?? (??:-1)
> 3: Jitrino::MemoryManager::_free_arenas(Jitrino::Arena*) (??:-1)
> 4: Jitrino::MemoryManager::~MemoryManager() (??:-1)
> 5: ?? (??:-1)
> 6: JIT_compile_method_with_params (??:-1)
> addr2line: '[stack]': No such file
> 7: ?? (IT_compile_method_with_params:-1)
> 8: ?? (??:-1)
> 9: Jitrino::MemoryManager::_free_arenas(Jitrino::Arena*) (??:-1)
> 10: Jitrino::MemoryManager::~MemoryManager() (??:-1)
> 11: ?? (??:-1)
> addr2line: '[stack]': No such file
> 12: ?? (itrino::MemoryManager::~MemoryManager():-1)
> 13: ?? (??:-1)
> addr2line: '[stack]': No such file
> 14: ?? (itrino::MemoryManager::~MemoryManager():-1)
> addr2line: '[stack]': No such file
> 15: ?? (itrino::MemoryManager::~MemoryManager():-1)
> addr2line: '[stack]': No such file
> 16: ?? (itrino::MemoryManager::~MemoryManager():-1)
> addr2line: '[stack]': No such file
> 17: ?? (itrino::MemoryManager::~MemoryManager():-1)
> <end of stack trace>
> gdb)
> #0 0x0000000000e41868 in ?? ()
> #1 0x00002aaaad3d04e8 in ?? ()
> #2 0x00002aab2b2d97d8 in ?? ()
> #3 0x00002aaac2fef870 in ?? ()
> #4 0x00002aaac2fef9c8 in ?? ()
> #5 0x00002aab2c24b0c1 in ?? ()
> #6 0x00002aaaad125d20 in Jitrino::LogStream::ison () from /home/lab_perfstat/rrafikov/platform/0620-lnx64/bin/default//libjitrino.so
> #7 0x00002aaaacde1fac in Jitrino::MemoryManager::_free_arenas ()
> from /home/lab_perfstat/rrafikov/platform/0620-lnx64/bin/default//libjitrino.so
> #8 0x00002aaaacde1f45 in Jitrino::MemoryManager::~MemoryManager ()
> from /home/lab_perfstat/rrafikov/platform/0620-lnx64/bin/default//libjitrino.so
> #9 0x00002aaaacd1e869 in JIT_compile_method_with_params ()
> from /home/lab_perfstat/rrafikov/platform/0620-lnx64/bin/default//libjitrino.so
> #10 0x0000000000000000 in ?? ()
> 2. The second one is if setting heap > 2G
> 10: ?? (??:-1)
> addr2line: '[stack]': No such file
> 11: ?? (:-1)
> 12: ?? (??:-1)
> 13: ?? (??:-1)
> 14: ?? (??:-1)
> 15: ?? (??:-1)
> addr2line: '[stack]': No such file
> 16: ?? (:-1)
> 17: ?? (??:-1)
> 18: ?? (??:-1)
> 19: org/apache/harmony/nio/FileChannelFactory.getFileChannel(Ljava/lang/Object;JI)Ljava/nio/channels/FileChannel; (FileChannelFactory.java:-1)
> 20: java/io/FileOutputStream.<init>(Ljava/io/FileDescriptor;)V (FileOutputStream.java:126)
> 21: java/lang/System.createErr()Ljava/io/PrintStream; (System.java:347)
> 22: java/lang/System.<clinit>()V (System.java:59)
> 23: ?? (??:-1)
> 24: java/lang/ThreadGroup.checkAccess()V (ThreadGroup.java:174)
> 25: java/lang/ThreadGroup.<init>(Ljava/lang/ThreadGroup;Ljava/lang/String;)V (ThreadGroup.java:97)
> 26: java/lang/Thread.<init>(Ljava/lang/ThreadGroup;Ljava/lang/String;JJIZ)V (Thread.java:226)
> <end of stack trace>
> In this case gdb back trace is not informative:
> (gdb) bt
> #0 0x00000000005485b8 in ?? ()
> #1 0x00002aaaad3619d6 in ?? ()
> #2 0x00002aaac3fb0bb0 in ?? ()
> #3 0x0000000000000000 in ?? ()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.