<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Operating Systems</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Operating Systems feed</description>
    <item>
      <title>Article: The iOS Crash We Could Not Reproduce</title>
      <link>https://www.infoq.com/articles/ios-crash-sigbus-debugging-experiment/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Operating+Systems</link>
      <description>&lt;img src="https://res.infoq.com/articles/ios-crash-sigbus-debugging-experiment/en/headerimage/ios-crash-sigbus-debugging-experiment-header-1793282827397.jpg"/&gt;&lt;p&gt;This article describes the investigation to find the root cause of a production crash in a large-scale iOS consumer app that had no clean stack trace. The crash occurred intermittently and resisted every local reproduction attempt. The final code change was small, but identifying the root cause required turning a vague SIGBUS report into a controlled set of experiments.&lt;/p&gt; &lt;i&gt;By Abhishek Gang Deb&lt;/i&gt;</description>
      <category>iOS</category>
      <category>Debugging</category>
      <category>Concurrency</category>
      <category>Mobile</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 11 Nov 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ios-crash-sigbus-debugging-experiment/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Operating+Systems</guid>
      <dc:creator>Abhishek Gang Deb</dc:creator>
      <dc:date>2026-11-11T09:00:00Z</dc:date>
      <dc:identifier>/articles/ios-crash-sigbus-debugging-experiment/en</dc:identifier>
    </item>
    <item>
      <title>Article: The App Is Just the Tip: What It Takes to Build Mobile Infrastructure at Scale</title>
      <link>https://www.infoq.com/articles/mobile-app-infrastructure-at-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Operating+Systems</link>
      <description>&lt;img src="https://res.infoq.com/articles/mobile-app-infrastructure-at-scale/en/headerimage/mobile-app-infrastructure-at-scale-header-1793263251757.jpg"/&gt;&lt;p&gt;What determines whether your app feels fast, ships often, and stays stable at scale is not the app itself. It is what sits behind it. This article is about that layer: what it does, why it exists, what it takes to design it correctly, and what happens when you try to migrate a live, high-traffic product onto it without a safety net.&lt;/p&gt; &lt;i&gt;By Kirill Sokolov&lt;/i&gt;</description>
      <category>iOS</category>
      <category>REST</category>
      <category>API</category>
      <category>Architecture</category>
      <category>Microservices</category>
      <category>Android</category>
      <category>Mobile</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 04 Nov 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/mobile-app-infrastructure-at-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Operating+Systems</guid>
      <dc:creator>Kirill Sokolov</dc:creator>
      <dc:date>2026-11-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/mobile-app-infrastructure-at-scale/en</dc:identifier>
    </item>
  </channel>
</rss>
