Crash with release_C_heap_structures

[Coleen Phillimore]

We don't have any reports of crashes in this code currently. Please file 
a bug with (hopefully) directions to reproduce.
Thanks!
Coleen

On 12/19/14, 12:59 AM, David Holmes wrote:
> Hi Denis,
>
> On 18/12/2014 11:31 PM, Denis Fokin wrote:
>> Hi,
>>
>> I see a couple conversations on the list about 
>> release_C_heap_structures issues.
>>
>> I still get a lot of reports about crashes even with early access 
>> jdk8u40 on Mac OS X 10.10
>>
>> Process:               java [53007]
>> Path: 
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
>> Identifier:            net.java.openjdk.cmd
>> Version:               1.0 (1.0)
>> Code Type:             X86-64 (Native)
>> Parent Process:        idea [44131]
>> Responsible:           idea [44131]
>> User ID:               503
>>
>> Thread 8 Crashed:
>> 0   libsystem_kernel.dylib        0x00007fff8e3fe282 __pthread_kill + 10
>> 1   libsystem_c.dylib             0x00007fff9cadfb73 abort + 129
>> 2   libsystem_malloc.dylib        0x00007fff965c9937 free + 428
>> 3   libjvm.dylib                  0x00000001043340d1 
>> InstanceKlass::release_C_heap_structures() + 499
>> 4   libjvm.dylib                  0x000000010433b548 
>> InstanceKlass::deallocate_contents(ClassLoaderData*) + 48
>> 5   libjvm.dylib                  0x0000000104211f28 void 
>> MetadataFactory::free_metadata<InstanceKlass*>(ClassLoaderData*, 
>> InstanceKlass*) + 69
>> 6   libjvm.dylib                  0x0000000104210f01 
>> ClassLoaderData::free_deallocate_list() + 177
>> 7   libjvm.dylib                  0x0000000104210f97 
>> ClassLoaderDataGraph::do_unloading(BoolObjectClosure*) + 105
>> 8   libjvm.dylib                  0x0000000104599da8 
>> SystemDictionary::do_unloading(BoolObjectClosure*) + 18
>> 9   libjvm.dylib                  0x00000001045265b6 
>> PSParallelCompact::marking_phase(ParCompactionManager*, bool, 
>> ParallelOldTracer*) + 1322
>> 10  libjvm.dylib                  0x0000000104527adc 
>> PSParallelCompact::invoke_no_policy(bool) + 1108
>> 11  libjvm.dylib                  0x000000010452bdd8 
>> PSScavenge::invoke() + 214
>> 12  libjvm.dylib                  0x0000000104501217 
>> ParallelScavengeHeap::failed_mem_allocate(unsigned long) + 39
>> 13  libjvm.dylib                  0x000000010460f4fe 
>> VM_ParallelGCFailedAllocation::doit() + 74
>> 14  libjvm.dylib                  0x0000000104615b05 
>> VM_Operation::evaluate() + 79
>> 15  libjvm.dylib                  0x0000000104614171 
>> VMThread::evaluate_operation(VM_Operation*) + 223
>> 16  libjvm.dylib                  0x00000001046145be VMThread::loop() 
>> + 808
>> 17  libjvm.dylib                  0x0000000104613edd VMThread::run() 
>> + 121
>> 18  libjvm.dylib                  0x00000001044efa42 
>> java_start(Thread*) + 246
>> 19  libsystem_pthread.dylib       0x00007fff9b0d52fc _pthread_body + 131
>> 20  libsystem_pthread.dylib       0x00007fff9b0d5279 _pthread_start + 
>> 176
>> 21  libsystem_pthread.dylib       0x00007fff9b0d34b1 thread_start + 13
>>
>> Has the issue been resolved at least in jdk9? If not is it something 
>> new or a well known issue?
>
> I can't find any bugs reports relating to this, so it seems not to be 
> a known issue. google search didn't turn up anything either.
>
> Where has this been seen?
>
> David
>
>> Thank you,
>>     Denis.
>>