Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adguard 6.2.390 at Windows 10 stops browsing until user kill the process #1901

Closed
altokarev opened this issue Aug 24, 2017 · 25 comments
Closed

Adguard 6.2.390 at Windows 10 stops browsing until user kill the process #1901

altokarev opened this issue Aug 24, 2017 · 25 comments
Assignees
Labels
Milestone

Comments

@altokarev
Copy link
Member

@altokarev altokarev commented Aug 24, 2017

Expected behavior

Surfing the Internet with no issues

Actual behavior

Adguard 6.2.390 randomly stops browsing after several minutes of use. After exiting Adguard the process doesn't stop and takes 16% CPU until user kills the process.

Related reports

Forum thread, 1439399

Environment

  • Google Chrome
  • Adguard v6.2.390.2018
  • Operating system and version: Windows 10, v.1703, build 15063.540
  • Hardware: Intel Core i7 3770k/16GB/SSD/GTX1070

Logs

@ameshkov ameshkov added this to the 6.2 milestone Aug 24, 2017
@ameshkov ameshkov added the bug label Aug 24, 2017
@fazlee712

This comment has been minimized.

Copy link

@fazlee712 fazlee712 commented Aug 25, 2017

Can confirm, also on W10 build 16273
i5-4690
Nvidia GTX 970

Adguard maintains about 30% of the CPU resource usage until forcibly ending the process (exiting the program normally does not actually stop the process despite explicitly selecting the option to not allow it to continue running). While this is happening (which starts anywhere between 5 seconds to 5 minutes from any filtered app/program starting a connection).

Chrome version doesn't seem to be relevant here as this behaviour can be seen without even launching Chrome – any app that tries to use a connection seems to be able to trigger it.

Rolling back to 6.2.379.1984 returns expected behaviour.

Unfortunately I don't actually have any useful logs :S

For what it's worth, it seems to not be occurring on my Surface Pro 3 (same Windows build)

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Aug 28, 2017

Rolling back to 6.2.379.1984 returns expected behaviour.

That's an important addition, we should check what has changed between 379 and 390.

@justmwa

This comment has been minimized.

Copy link

@justmwa justmwa commented Aug 29, 2017

Ditto, logs sent to support through app. Win1607Fr, ipv6 used. Happened both with Bitdefender and Windows Defender if it matters.

@altokarev

This comment has been minimized.

Copy link
Member Author

@altokarev altokarev commented Aug 30, 2017

@justmwa I can't find your message. Could you please specify your support service ticket ID? Thanks.

@justmwa

This comment has been minimized.

Copy link

@justmwa justmwa commented Aug 30, 2017

@altokarev

This comment has been minimized.

Copy link
Member Author

@altokarev altokarev commented Aug 30, 2017

I only have a personal support ID

Yeah, that ID. Could please name it to me?

@altokarev altokarev closed this Aug 30, 2017
@altokarev altokarev reopened this Aug 30, 2017
@justmwa

This comment has been minimized.

Copy link

@justmwa justmwa commented Aug 30, 2017

that would be 1616587

@altokarev

This comment has been minimized.

Copy link
Member Author

@altokarev altokarev commented Sep 1, 2017

CPU loop:
state.txt
debug.txt


Hey,

well it's easy, it's eating one full core (25% on a i5 quad):
actually it's even slightly more than that:
it's not shooting up right away, it takes a while (a bunch of specific queries coming from browsers I >guess) but when it gets there it won't stop until I kill the process.
I turned debug log on, I will send you them after I manage to figure out where they're stored and when I reproduced the issue :)

regards,
Martin.

Screenshots:

40941407
40988047


SSL_ERROR_RX_MALFORMED_ALERT:
state (1).txt
debug (1).txt

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 12, 2017

Possible dup of #1918

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 15, 2017

I don't have Logs, very sorry, I've also been having a problem with my Avira FREE A/V, losing the ability to save reports from updates, not sure if this is Adguard related. I'm running too much Beta software to give you accurate info. I have backed off Adguard Windows to 6.2.379.1984 and will continue with Avira FREE Beta until I can figure out this mess. Not trying to throw a Monkey Wrench into the problem...I know this has NOTHING to do with the original problem reported or that I saw, just some info

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 17, 2017

@Steve1209 hi! Could you please try the dev build from this comment: #1918 (comment)

One of the users affected by the issue reported that it helped. Maybe it will help in your case as well?

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 17, 2017

Andrey,

OK, I installed the Dev. version 6.2.396.2052 and we'll see what happens, I have debug logging enabled.

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 17, 2017

Seems like Adguard service is using a lot of CPU while doing nothing https://www.screencast.com/t/ZVWcNHD2PDu

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 17, 2017

@Steve1209 might be updating the browsing security filters. Give it some time and check if it's gone.

I can take a look at the logs if it does not stop in a couple of minutes.

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 17, 2017

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 17, 2017

@BooBerry

This comment has been minimized.

Copy link

@BooBerry BooBerry commented Sep 17, 2017

Log files are located in the hidden ProgramData folder found in the root of the boot drive (e.g. C:).

This is where the logs are located on my machine;

C:\ProgramData\Adguard\Logs

@Steve1209

This comment has been minimized.

Copy link

@Steve1209 Steve1209 commented Sep 17, 2017

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 17, 2017

Closing this issue as it is now clear that it's a duplicate of #1918

Thanks to @Steve1209 we've narrowed it down to the UDP filtering changes:
#1918 (comment)

@ameshkov ameshkov closed this Sep 17, 2017
@ameshkov ameshkov added duplicate and removed bug labels Sep 17, 2017
@ameshkov ameshkov removed the P2: High label Sep 17, 2017
@ameshkov ameshkov removed this from the 6.2 milestone Sep 17, 2017
@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 18, 2017

Aaand it appears that it was too early to close this bug.

My build helps with this particular issue, but not with Google Home issue.

@ameshkov ameshkov reopened this Sep 18, 2017
@ameshkov ameshkov added bug P2: High and removed duplicate labels Sep 18, 2017
@ameshkov ameshkov added this to the 6.2 milestone Sep 18, 2017
@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 21, 2017

Thanks to all the people who helped us with testing, we've finally fixed the issue yesterday.

Here is the build that helped:
https://uploads.adguard.com/up04_65uvi.exe

@ameshkov ameshkov closed this Sep 21, 2017
@fazlee712

This comment has been minimized.

Copy link

@fazlee712 fazlee712 commented Sep 21, 2017

@ameshkov Just installed https://uploads.adguard.com/up04_65uvi.exe over the 6.2.379 build, restarted PC and it immediately stopped working, exhibiting the original problematic behavior.

No logs unfortunately, as I have work that needs to be done, so I immediately just rolled back to .379 again and of course it's working as expected.

Will reproduce it over the weekend with logs if you still need it by then.

@BooBerry

This comment has been minimized.

Copy link

@BooBerry BooBerry commented Sep 21, 2017

That's likely the wrong build (there's so many to keep track of), so try this one (Andrey posted in the other GH issue):

https://uploads.adguard.com/up04_ji7em_setup_6.2.400_dev.exe

This is 6.2.400.

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 21, 2017

Sorry for all the confusion, that's a lesson for me on how to setup Monosnap properly:)

@ameshkov

This comment has been minimized.

Copy link
Member

@ameshkov ameshkov commented Sep 25, 2017

Guys, build .400 has a problem. It'd be better to install an updated one:
#1918 (comment)

@vozersky vozersky removed the beta label Sep 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.