From bb635d05be79565f35f44db92ada52b31cabf4e3 Mon Sep 17 00:00:00 2001
From: C3C0 <ceco@ceco.sk.eu.org>
Date: Wed, 6 Mar 2019 08:53:08 +0100
Subject: [PATCH] Perform explicit garbage collection before every
 backupAndHook

Gives GC a chance to do its work before every hook so there is less chance
it gets in the way in the middle of hooking procedure which does critical
memory block operations.
Attempts to fix GC related crashes such as those reported in #127
---
 .../main/java/com/elderdrivers/riru/xposed/core/HookMain.java    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Bridge/src/main/java/com/elderdrivers/riru/xposed/core/HookMain.java b/Bridge/src/main/java/com/elderdrivers/riru/xposed/core/HookMain.java
index 21ad22f1..846427f3 100644
--- a/Bridge/src/main/java/com/elderdrivers/riru/xposed/core/HookMain.java
+++ b/Bridge/src/main/java/com/elderdrivers/riru/xposed/core/HookMain.java
@@ -111,6 +111,7 @@ public class HookMain {
         if (backup != null) {
             HookMethodResolver.resolveMethod(hook, backup);
         }
+        Runtime.getRuntime().gc();
         if (!backupAndHookNative(target, hook, backup)) {
             throw new RuntimeException("Failed to hook " + target + " with " + hook);
         }