A bug in C2 that causes a large amount of physical memory to be allocated

[Baesken, Matthias]

Hi, should I remove the function  nmethod::print_calls   ? It looks like the function is unused .
Or is it left over to be called   from a debugger or something like this ?

Best regards, Matthias


> -----Original Message-----
> From: Aleksey Shipilev <shade at redhat.com>
> Sent: Freitag, 15. März 2019 13:22
> To: Baesken, Matthias <matthias.baesken at sap.com>; jdk8u-
> dev at openjdk.java.net; Hotspot dev runtime <hotspot-runtime-
> dev at openjdk.java.net>
> Subject: Re: A bug in C2 that causes a large amount of physical memory to be
> allocated
> 
> On 3/15/19 1:17 PM, Baesken, Matthias wrote:
> > nmethod::print_calls
> >
> > 3284    case relocInfo::opt_virtual_call_type: {
> > 3285      VerifyMutexLocker mc(CompiledIC_lock);
> > 3286      CompiledIC_at(&iter)->print();
> > 3287      break;
> > 3288    }
> >
> > Misses the Resourcemark too  (although   the coding might be unused (?) )
> ...
> 
> This one is guarded by #ifndef PRODUCT, so not as important. Feel free to
> submit another RFE to
> clean that up.
> 
> -Aleksey