<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Microsoft on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/microsoft/</link>
    <description>Recent content in Microsoft on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <image>
      <title>Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
      <url>https://netacoding.com/img/logo-netacoding.png</url>
      <link>https://netacoding.com/img/logo-netacoding.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/microsoft/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WebTransport Zombie Connections: RFC 9114 Trailer Frame Triggers Permanent Stream Leak &amp; OOM in Microsoft Edge and Chromium | Protocol RE</title>
      <link>https://netacoding.com/posts/webtransport-zombie/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/webtransport-zombie/</guid>
      <description>Sending a trailer HEADERS frame without END_STREAM on a WebTransport CONNECT stream causes Microsoft Edge and Chromium to permanently hold QUIC connections open, driving Network Service memory from 6 MB to 339 MB with 5,000 connections before an OOM crash. A secondary bug delivers server datagrams to JS on sessions the H3 layer considers closed. Root cause is in the shared quiche QUIC library. Reported to both MSRC and Google Chrome VRP — closed without fix by both vendors.</description>
    </item>
  </channel>
</rss>
