Transaction

jmetaB033e09315b1c09701456786b14c73feb36d28fa8785d93794ad827e15a07611060@6e310a0579acad2cd4035426f1abe6c508d443dd4241600efb7c245ddb21c7da atom.entrymetarss.netM“<entry> <title type="text">NSCopyObject, the griefer that keeps on griefing</title> <id>https://wadetregaskis.com/nscopyobject-the-griefer-that-keeps-on-griefing/</id> <updated>2024-07-17T08:01:16.066457Z</updated> <link href="https://wadetregaskis.com/nscopyobject-the-griefer-that-keeps-on-griefing/"/> <author> <name>chmaynard</name> <uri>https://news.ycombinator.com/user?id=chmaynard</uri> </author> <content type="html">&lt;img src=&#34;https://wadetregaskis.com/wp-content/uploads/2024/07/grumpy-cat-no.avif&#34; style=&#34;width: 220px; height: 173px;&#34; /&gt;&lt;br /&gt;NSCopyObject is a problematic Foundation function that can cause memory leaks and crashes when used with ARC-managed objects. Apple&#39;s continued use of NSCopyObject in their own frameworks and lack of a replacement copy mechanism has led to a decade-long struggle for developers to work around its issues. &lt;a href=&#34;https://hackernews.betacat.io/#nscopyobject-the-griefer-that-keeps-on-griefing&#34; target=&#34;_blank&#34;&gt;[summary]&lt;/a&gt; &lt;a href=&#34;https://news.ycombinator.com/item?id=40976474&#34; target=&#34;_blank&#34;&gt;[comments]&lt;/a&gt;</content> </entry>