harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Leviev (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-5331) [drlvm][gc] memory leak at hashcode_buf_create at hashcode.h while EIOffice run
Date Wed, 19 Dec 2007 17:38:43 GMT
[drlvm][gc] memory leak at hashcode_buf_create at hashcode.h while EIOffice run
-------------------------------------------------------------------------------

                 Key: HARMONY-5331
                 URL: https://issues.apache.org/jira/browse/HARMONY-5331
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
         Environment: wim32
            Reporter: Ilya Leviev


memory leak at hashcode_buf_create at hashcode.h while EIOffice run

svn = r605216


While profiling a simple EIOffice application on Harmony using 
BoundsChecker, the tool detected following memory leaks. 

"hashcode_buf" not disposed correctly while EIOffice run. 
The issue also reproduced while java2demo run. 

Here is stack trace: 

Memory Leak  allocated by malloc.

hashcode_buf_create	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\common\hashcode.h	85

 line 85: Hashcode_Buf* hashcode_buf = (Hashcode_Buf*) STD_MALLOC(sizeof(Hashcode_Buf));

block_init	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\common\gc_block.h	109
space_init_blocks	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\common\gc_space.h	138
mspace_initialize	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\mark_compact\mspace.cpp	70
gc_mos_initialize	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\gen\gen.cpp	315
gc_gen_initialize	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\gen\gen.cpp	223
gc_init	c:\home\os\hy2\trunk\working_vm\vm\gc_gen\src\common\gc_for_vm.cpp	102
vm_init1	c:\home\os\hy2\trunk\working_vm\vm\vmcore\src\init\vm_init.cpp	789
JNI_CreateJavaVM	c:\home\os\hy2\trunk\working_vm\vm\vmcore\src\jni\jni.cpp	499
vmdlldir_parseCmdLine	C:\home\os\hy2\trunk\working_vm\build\win_ia32_msvc_debug\deploy\jdk\jre\bin\java.exe!0x0000011d





-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message