AdguardTeam / AdguardTeam/AdguardForWindows
Discovery+ (play.discoveryplus.com): brightline.tv / litix.io scripts spam requests without backoff, causing sustained high CPU
- 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
n/a
### Browser version
n/a
### OS version
n/a
### Traffic filtering
- [ ] yes, I do
### Ad Blocking
_No response_
### Privacy
_No response_
### Social
_No response_
### Annoyances
_No response_
### Security
_No response_
### Other
_No response_
### Language-specific
_No response_
### Which DNS server do you use?
DNS protection disabled
### DNS protocol
None
### Custom DNS
_No response_
### What Stealth Mode options do you have enabled?
_No response_
### Support ticket ID
_No response_
### Issue Details
https://www.reddit.com/r/uBlockOrigin/comments/1w22p91/discovery_playdiscoverypluscom_adtech_scripts/
### Expected Behavior
_No response_
### Actual Behavior
The problem: two ad-tech vendors' scripts — [brightline.tv](http://brightline.tv/) and [litix.io](http://litix.io/) — retry their requests continuously with no backoff, for as long as the tab stays open. Tens of thousands of requests over a session, tens of MB transferred. This was drawing over twice the pc's idle power.
### Screenshots
Screenshot 1
### Additional Information
Results:
CPU: 10%+ sustained → under 1%
Requests: tens of thousands over minutes → ~6 over 20 minutes
Also tested three configurations for comparison:
No blocker at all: moderate, rising CPU (2-4%)
Blocker on, without these filters: worst result — high CPU (8-10%)
Blocker on, with these filters: best result — under 1%
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.