AdguardTeam / AdguardTeam/AdguardForWindows

Adguard 8.0 causes "uncloseable" connections in some applications, hanging them in kernel space

Abierto
#5,528 10 comentarios 1 reacción 1 asignado Asignado a @northis Ver en GitHub
Priority: P4 tech Version: AdGuard v8.2
Lenguaje dominante
Sin datos de lenguaje
Estrellas
887
Forks
84
Merge medio
27 min
PR fusionados (30 d)
2

Descripción

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

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

8.0

### Browser version

Not applicable

### OS version

Windows 10 22H2

### Traffic filtering

- [x] yes, I do

### Ad Blocking

AdGuard Base filter

### Privacy

_No response_

### Social

_No response_

### Annoyances

_No response_

### Security

_No response_

### Other

_No response_

### Language-specific

AdGuard Russian filter

### Which DNS server do you use?

System default DNS

### DNS protocol

Regular

### Custom DNS

_No response_

### What Stealth Mode options do you have enabled?

_No response_

### Support ticket ID

_No response_

### Issue Details

Steps to reproduce:
Don't have reliable steps to reproduce the issue, but, for example, running Steam for long enough *with* it being routed through AdGuard causes this issue. **If you disable "route traffic through adguard" for steam, issue goes away**.

If it helps, I *do* use Window's sleep feature (put PC to low-power state instead of powering it off).

### Expected Behavior

Apps don't hang inside socket close kernel call.

### Actual Behavior

Screenshot 1

![Image](https://github.com/user-attachments/assets/cedf4713-b79b-457b-a212-b131e7035647)

Stopping AdGuard service immediately resolves the issue for affected apps.

Приложения "зависают" внутри системных вызовов намертво (т.е. процесс/поток убить нельзя ничем), steam.exe сверху уже находился в процессе завершения работы. Такое происходило ранее, и причём опять же, чаще всего со стимом, но в определённой версии в ветке 7 это было исправлено и такое более не повторялось, а при обновлении до 8 оно вернулось вновь.

### Screenshots

Screenshot 2

![Image](https://github.com/user-attachments/assets/2edef34f-68a8-433d-b141-33991edd0419)

Video demo

https://github.com/user-attachments/assets/30c0bfb3-016a-4f6a-88c4-ea5a058ade14

### Additional Information

_No response_

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.