When you change settings in the Adguard app, Adguard crashes

[michael1900]

Prerequisites

Please answer the following questions for yourself before submitting an issue.

• [*] I am running the latest version
• [*] I checked the documentation and found no answer
• [*] I checked to make sure that this issue has not already been filed

Issue Details

  When i boot the phone Adguard works well. After some time, no much, if i try to change something in Adguard app, not something in particular, anything, Adguard crash and all the phone remains stuck, completely stuck and only way is reboot it every single time.

• AdGuard version: Both last nightly and stable version
• Filtering mode: Local VPN
• Device: Honor Magic 4 Pro
• Operating system and version: Android 12
• Root access: No

Expected Behavior

   No crash

Actual Behavior

   Crash and the only way to use again adguard AND the phone is reboot this last

How can solve this and how can help you to fix this strange and really tedious bug? I have no one problem with Mate 20 Pro with android 10.

Edit: logs file --> https://www.upload.ee/files/14365680/adguard_logs_3.6.46_2707_205608.zip.html Problem starts to 20:52

[michael1900]

@artemiv4nov @Stillness-2 @sfionov hi all, why no one help?

[michael1900]

Someone can help me, please?

[maxikuzmin]

@michael1900 looks like a problem with the device itself. Our log just crashes after the protection start message. We need the exact time of the problem

To troubleshoot this issue, we need to get additional logs.

Here's what we need you to do:

• Collect the debug log as it's explained here;
• Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
• Additionally, capture the system bug report after reproducing the issue. Here's the instruction;
• Send both files to [email protected]. Mention the Github issue number and the exact time when the issue was reproduced.

[michael1900]

The log is there. If i take a new log it will be exactly the same. The right time also, problem starts at 20.52/54, maybe a bit later but it's all there.

[maxikuzmin]

@michael1900 looks like a problem with the device itself. Our log just crashes after the protection start message. We need to overwrite the logs. Please repeat the problem and send the logs again with the time of the problem

[maxikuzmin]

@michael1900 any news?

[michael1900]

But if i repeat the log we will have always the same problem "with the device itself" so what's the purpose of a new log with the same procedure? After some minutes AdGuard crashes/stucks so there is nothing that i can do. The log will be the same that before.

[ihurin]

@michael1900 just make them, please.

[michael1900]

@michael1900 just make them, please.

https://www.upload.ee/files/14422664/adguard_logs_4.0.77_1708_101336.zip.html

10.10 am

@artemiv4nov @Stillness-2 @sfionov

[michael1900]

Hi. So there will be a fix for this awful bug?

[maxikuzmin]

@michael1900 we're looking into. Please wait

[michael1900]

@michael1900 we're looking into. Please wait

Can i have an update on this?

[maxikuzmin]

@michael1900 thanks for the wait. For a more detailed analysis, we need a logcat log from you. Here's how you can do it https://kb.adguard.com/en/android/solving-problems/logcat

[michael1900]

@michael1900 thanks for the wait. For a more detailed analysis, we need a logcat log from you. Here's how you can do it https://kb.adguard.com/en/android/solving-problems/logcat

Oh God!

https://www.upload.ee/files/14443668/bugreport-LGE-NX9EEA-HONORLGE-N49-2022-08-24-14-37-58.zip.html

Please fix this bug, I don't know what else to do!

@maxikuzmin @artemiv4nov @Stillness-2 @sfionov

[maxikuzmin]

@michael1900 we're looking into the problem. Please wait

[michael1900]

@michael1900 we're looking into the problem. Please wait

I see that the status is solved in core lib thread. I need the new nightly apk

[michael1900]

What a shame. Really what a shame. @sfionov @artemiv4nov @admitrevskiy @maxikuzmin @Chinaski1 @Stillness-2 @ameshkov

[ameshkov]

We at first supposed that the problem is in CoreLibs. It was not confirmed by a newer portion of logs, it's like the problem happens randomly in different places of the code.

Since it only happens with your device, we tend to think that it may be triggered by a rare firmware bug.

It would help if you upgrade once again to the latest available nightly apk and collect the logs again.

Please note, that we'll need both AG debug logs AND an Android bug report so that we could compare the timing there, and compare it with the previous bug report.

[maxikuzmin]

@michael1900 any news?

[maxikuzmin]

@michael1900 I am closing this issue while. Later, if you still have the problem, you can send logs with timing from the new version and reopen the issue.