search

theapache64 / dex-diff

A tool to compare two APK files at the dex level. Useful for checking the impact of things like fullMode and dex optimisations.
100 stars 2 forks source link

`Comparing before and after` never finishes #1

Open SimonMarquis opened 1 week ago

SimonMarquis commented 1 week ago

👋 Hi, we have a quite large app ~80MiB, and the process never finishes. It is stuck at this step: ➡️ Comparing before and after... (this may take some time)

I was wondering if there was a way to configure the max heapSize or CPU for this tool (RAM is probably the limiting factor)?

⚔️ dex-diff v0.0.6
🚀 Initialising...
➡️ Deleting old results (dex-diff-result)...
✅ Deleted old results
➡️ Decompiling before APK... (this may take some time)
✅ Decompiling before APK finished
➡️ Decompiling after APK... (this may take some time)
✅ Decompiling after APK finished
✅ Decompile finished (403417ms)
➡️ Comparing before and after... (this may take some time)
theapache64 commented 1 week ago

Hi Simon,

80MiB sounds quite large. how much time you waited for the comparison to happen? I just published 0.0.6's jar here -> https://github.com/theapache64/dex-diff/releases/tag/0.0.6 You can try modifying the memory params like this

java -jar -Xms4096M -Xmx8192M dex-diff.main.jar  before.apk after.apk
com.my.app

Let me know if it worked or not.

On Fri, Jun 14, 2024 at 5:16 PM Simon Marquis @.***> wrote:

👋 Hi, we have a quite large app ~80MiB, and the process never finishes. It is stuck at this step: ➡️ Comparing before and after... (this may take some time)

I was wondering if there was a way to configure the max heapSize or CPU for this tool (RAM is probably the limiting factor)?

— Reply to this email directly, view it on GitHub https://github.com/theapache64/dex-diff/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJ23R2SRJFHY5ZSOZEJWS3ZHLJYJAVCNFSM6AAAAABJKGIE7WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2TGMJZGUYTKOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

SimonMarquis commented 1 week ago

Like a few hours 🙈 I'll try manually setting the heap size with the jar executable next week 👍

SimonMarquis commented 1 week ago

Allocating 16G seems to have make it work! Though, heap size usage and CPU dropped during the last step, there might be something else throttling the process...

image