1
81%
main: 92%

Ran 14 Jul 2024 09:39PM UTC

Files 156

Run time 3s

Badge

Embed ▾

Committed 14 Jul 2024 09:30PM UTC coverage: 80.663% (+0.03%) from 80.634%

Job # #1197.1

Build Type

push

travis-ci

Committed by

bradh352

Commit Message

Rework WinAFD event code (#811)

We've had reports of user-after-free type crashes in Windows cleanup
code for the Event Thread. In evaluating the code, it appeared there
were some memory leaks on per-connection handles that may have remained
open during shutdown, while trying to resolve that it became apparent
the methodology chosen may not have been the right one for interfacing
with the Windows AFD system as stability issues were seen during this
debugging process.

Since this system is completely undocumented, there was no clear
resolution path other than to switch to the *other* methodology which
involves directly opening `\Device\Afd`, rather than spawning a "peer
socket" to use to queue AFD operations.

The original methodology chosen more closely resembled what is employed
by [libuv](https://github.com/libuv/libuv) and given its widespread use
was the reason it was used. The new methodology more closely resembles
[wepoll](https://github.com/piscisaureus/wepoll).

Its not clear if there are any scalability or performance advantages or
disadvantages for either method. They both seem like different ways to
do the same thing, but this current way does seem more stable.

Fixes #798
Fix By: Brad House (@bradh352)

Coverage Stats

8710 of 10798 relevant lines covered (80.66%)

3773.18 hits per line

c-ares / c-ares / #1197 / 1
81%
main: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #1197.1

c-ares / c-ares / #1197 / 1 81% main: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #1197.1

c-ares / c-ares / #1197 / 1
81%
main: 92%

README BADGES
x