Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

Commit

Permalink
Don't do heap dump on SIGUSR1.
Browse files Browse the repository at this point in the history
We still do the GC, but without the HPROF heap dump.

Change-Id: I004a65b9571667dd320dfabec1441d0fc8b9970a
  • Loading branch information
fadden committed Jul 16, 2010
1 parent 58b0f67 commit b037a46
Showing 1 changed file with 1 addition and 10 deletions.
11 changes: 1 addition & 10 deletions vm/SignalCatcher.c
Expand Up @@ -211,21 +211,12 @@ static void handleSigQuit(void)
}

/*
* Respond to a SIGUSR1 by forcing a GC. If we were built with HPROF
* support, generate an HPROF dump file.
*
* (The HPROF dump generation is not all that useful now that we have
* better ways to generate it. Consider removing this in a future release.)
* Respond to a SIGUSR1 by forcing a GC.
*/
static void handleSigUsr1(void)
{
#if WITH_HPROF
LOGI("SIGUSR1 forcing GC and HPROF dump\n");
hprofDumpHeap(NULL, -1, false);
#else
LOGI("SIGUSR1 forcing GC (no HPROF)\n");
dvmCollectGarbage(false);
#endif
}

#if defined(WITH_JIT) && defined(WITH_JIT_TUNING)
Expand Down

0 comments on commit b037a46

Please sign in to comment.