<div dir="ltr">Thanks for the info!<div><br></div><div>FWIW, most of the places I have encountered this so far have made use of `URLComponents`, and have even been able to eliminate the crash by getting rid of that code in a few places. The other JIRA bug on this topic also mentions URLComponents in their repro case. Seems to be the culprit.</div><div><br></div><div>Also worth noting that in the above cases dealing with URLComponents the crash only happens in DEBUG compilations, not RELEASE.</div><div><br></div><div>However, I do have another one of these crashes that _does_ happen on RELEASE builds that I haven’t yet been able to reduce.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Nov 29, 2017 at 4:43 PM Tony Parker <<a href="mailto:anthony.parker@apple.com">anthony.parker@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Hi Brandon,<div><br></div><div>This is probably a bug in the CoreFoundation C sources part of swift-corelibs-foundation. Unlike Darwin platforms, we can’t make the CFSTR(“”) macro produce a CFStringRef that cannot be overreleased. Probably there is a constant string returned from CF function, then the Swift runtime assumes it can release it, and bam we wind up with an overrelease.</div><div><br></div><div>We’ll have to track down which function is getting called, which probably just requires stepping through that test case with a debugger…</div><div><br></div><div></div></div><div style="word-wrap:break-word;line-break:after-white-space"><div>- Tony<br></div></div><div style="word-wrap:break-word;line-break:after-white-space"><div><div><blockquote type="cite"><div>On Nov 29, 2017, at 1:34 PM, Brandon Williams via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>> wrote:</div><br class="m_-9212223342634817513Apple-interchange-newline"></blockquote></div></div></div><div style="word-wrap:break-word;line-break:after-white-space"><div><div><blockquote type="cite"><div><div dir="ltr"><div>Hello all!</div><div><br></div><div>We’ve been encountering this runtime error quite a bit recently, and we have no idea why. We’ve filed a bug and there’s one other on JIRA related to this, but both without any comments:</div><div><br></div><a href="https://bugs.swift.org/browse/SR-6422" target="_blank">https://bugs.swift.org/browse/SR-6422</a><br><div><a href="https://bugs.swift.org/browse/SR-6398" target="_blank">https://bugs.swift.org/browse/SR-6398</a><br></div><div><br></div><div>We’re curious if others are aware of this and or has more info? Is it a red herring for some other problem?</div><div><br></div><div>Any info would be helpful!</div></div></div></blockquote></div></div></div><div style="word-wrap:break-word;line-break:after-white-space"><div><div><blockquote type="cite"><div>
_______________________________________________<br>swift-corelibs-dev mailing list<br><a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br></div></blockquote></div></div></div></blockquote></div>