<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:admin="http://webns.net/mvcb/"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:hatena="http://www.hatena.ne.jp/info/xmlns#"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
>

<channel rdf:about="https://b.hatena.ne.jp/entry/s/railsatscale.com/2024-07-09-finding-memory-leaks-in-the-ruby-ecosystem/">
<title>&#x306F;&#x3066;&#x306A;&#x30D6;&#x30C3;&#x30AF;&#x30DE;&#x30FC;&#x30AF; - Finding Memory Leaks in the Ruby Ecosystem</title>
<link>https://b.hatena.ne.jp/entry/s/railsatscale.com/2024-07-09-finding-memory-leaks-in-the-ruby-ecosystem/</link>
<description>This blog post is adapted from a talk that Adam Hess and I gave at RubyKaigi 2024. Until recently, Ruby lacked a mechanism for detecting native-level memory leaks from within Ruby and native gems. ...</description>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="https://b.hatena.ne.jp/d6rkaiz/20240712#bookmark-4756157822786410912" />
  <rdf:li rdf:resource="https://b.hatena.ne.jp/Watson/20240712#bookmark-4756157822786410912" />
  <rdf:li rdf:resource="https://b.hatena.ne.jp/toshikish/20240712#bookmark-4756157822786410912" />
  <rdf:li rdf:resource="https://b.hatena.ne.jp/YassLab/20240712#bookmark-4756157822786410912" />
  <rdf:li rdf:resource="https://b.hatena.ne.jp/diveintounlimit/20240712#bookmark-4756157822786410912" />
  <rdf:li rdf:resource="https://b.hatena.ne.jp/xef/20240711#bookmark-4756157822786410912" />
 </rdf:Seq>
</items>
</channel>
<item rdf:about="https://b.hatena.ne.jp/d6rkaiz/20240712#bookmark-4756157822786410912">
<title>d6rkaiz</title>
<link>https://b.hatena.ne.jp/d6rkaiz/20240712#bookmark-4756157822786410912</link>
<description></description>
<dc:date>2024-07-12T14:29:54Z</dc:date>
</item>
<item rdf:about="https://b.hatena.ne.jp/Watson/20240712#bookmark-4756157822786410912">
<title>Watson</title>
<link>https://b.hatena.ne.jp/Watson/20240712#bookmark-4756157822786410912</link>
<description></description>
<dc:date>2024-07-12T04:39:05Z</dc:date>
<dc:subject>ruby</dc:subject>
<taxo:topics>
  <rdf:Bag>
    <rdf:li resource="https://b.hatena.ne.jp/q/ruby" />
  </rdf:Bag>
</taxo:topics>
</item>
<item rdf:about="https://b.hatena.ne.jp/toshikish/20240712#bookmark-4756157822786410912">
<title>toshikish</title>
<link>https://b.hatena.ne.jp/toshikish/20240712#bookmark-4756157822786410912</link>
<description></description>
<dc:date>2024-07-12T04:15:45Z</dc:date>
</item>
<item rdf:about="https://b.hatena.ne.jp/YassLab/20240712#bookmark-4756157822786410912">
<title>YassLab</title>
<link>https://b.hatena.ne.jp/YassLab/20240712#bookmark-4756157822786410912</link>
<description>&#x201C;Another limitation of ruby_memcheck is that it is limited to Linux systems since Valgrind only runs on Linux. This means that we cannot use a faster memory checker like Google&#x2019;s sanitizers or support other operating systems such as using the macOS leaks tool.&#x201D;</description>
<dc:date>2024-07-12T02:50:43Z</dc:date>
<dc:subject>Ruby</dc:subject>
<dc:subject>Memory</dc:subject>
<dc:subject>Shopify</dc:subject>
<taxo:topics>
  <rdf:Bag>
    <rdf:li resource="https://b.hatena.ne.jp/q/Ruby" />
    <rdf:li resource="https://b.hatena.ne.jp/q/Memory" />
    <rdf:li resource="https://b.hatena.ne.jp/q/Shopify" />
  </rdf:Bag>
</taxo:topics>
</item>
<item rdf:about="https://b.hatena.ne.jp/diveintounlimit/20240712#bookmark-4756157822786410912">
<title>diveintounlimit</title>
<link>https://b.hatena.ne.jp/diveintounlimit/20240712#bookmark-4756157822786410912</link>
<description>&#x3053;&#x308C;&#x306F;&#x5927;&#x5909;&#x3060;</description>
<dc:date>2024-07-11T23:58:19Z</dc:date>
</item>
<item rdf:about="https://b.hatena.ne.jp/xef/20240711#bookmark-4756157822786410912">
<title>xef</title>
<link>https://b.hatena.ne.jp/xef/20240711#bookmark-4756157822786410912</link>
<description></description>
<dc:date>2024-07-11T13:55:05Z</dc:date>
<dc:subject>Ruby</dc:subject>
<dc:subject>Debugging</dc:subject>
<taxo:topics>
  <rdf:Bag>
    <rdf:li resource="https://b.hatena.ne.jp/q/Ruby" />
    <rdf:li resource="https://b.hatena.ne.jp/q/Debugging" />
  </rdf:Bag>
</taxo:topics>
</item>
</rdf:RDF>