What are the implications of VMDebug.startGC in traceview file

Question

What are the implications of VMDebug.startGC in traceview file

The documentation says:

/* * Fake method, inserted into dmtrace output when the garbage collector * runs. Not actually called. */ private static void startGC() {} 

But in my tracking, I see something like this:

The muscles above the brown squares show that they are VMDebug.startGC () methods, with each method taking approximately 17 real ms. The green squares are BitmapFactory.nativeDecodeAssetFunctions, each taking about 26 real milliseconds. In this code segment, I load raster images for import as openGL textures.

What is the startGC () function?

I have faith based on the name of the function and the observation when they call it one way or another related to garbage collection, but the documentation contradicts me.

Answer 1

You have copied and entered the document description for the startClassPrep() method, which is below startGC() in the sources.

Real Description:

 /* * Fake method, inserted into dmtrace output when the garbage collector * runs. Not actually called. */ private static void startGC() {} 

It seems that this method is used only for debugging purposes when running traceview.