Ticket #153 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Crash on `p_setupPubElements` and CFURL cache

Reported by: jppavao Owned by:
Priority: critical Milestone: 1.0
Component: GUI Version: version 0.8
Keywords: Cc:

Description

There seems to be some thread safety issues plaguing the initial setup of the ad banner WebView?. Sometimes, during the application startup, either the main thread crashes somewhere inside p_setupPubElements, or the secondary thread checking for app updates crashes on one of the CFURL functions. In either case, the backtrace always shows that these two threads are in that state when the crash occurs: the main thread on the ad banner setup code, and the update checker on some CFURL function.

Attachments

crash sapo msg 1.txt (26.7 KB) - added by jppavao 5 years ago.
crash sapo msg 2.txt (28.2 KB) - added by jppavao 5 years ago.
SAPO Messenger_2008-01-24-104922_Leapfrog-iMac.crash (27.7 KB) - added by jppavao 5 years ago.
SAPO Messenger_2008-01-25-113845_Leapfrog-iMac.crash (28.1 KB) - added by jppavao 5 years ago.

Change History

Changed 5 years ago by jppavao

Changed 5 years ago by jppavao

Changed 5 years ago by jppavao

Changed 5 years ago by jppavao

Changed 5 years ago by jppavao

Started  this thread on the  macnetworkprog@lists.apple.com mailing list.

Also filed a bug report about this on Apple's bug reporter. Problem ID:  5706920

Changed 5 years ago by jppavao

(In [226]) Delayed the initial automatic check for updates for some seconds as an attempt to work around a crash involving two threads messing with the CFURL cache at the same time. References #153.

Changed 5 years ago by jppavao

Let's wait a while and see whether [226] really worked around these crashes successfully. We can close the ticket some days from now if no more crashes are reported.

Changed 5 years ago by jppavao

  • status changed from new to closed
  • resolution set to fixed

There were some fixes to a thread race condition in NSURLConnection's cache management (CVE-ID: CVE-2008-0058) that were made available in Security Update 2008-002. This, together with our small workaround and also the absence of any new related crash reports, oficially marks the issue as being fixed.

Note: See TracTickets for help on using tickets.