• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CFRunLookFindMode crash - revisited
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFRunLookFindMode crash - revisited


  • Subject: Re: CFRunLookFindMode crash - revisited
  • From: Martin Redington <email@hidden>
  • Date: Wed, 6 Dec 2006 03:50:12 +0000


Damn and blast.

I tried to adapt the Mandelbrot Example from Advanced Mac OS X programming to show this (http://www.borkware.com/corebook/second- edition-files/23-do-threads.tar.gz for the original), as it actually does something in the worker thread.

Sure enough, if I just stopped the threads it leaked ports, but with the fixes to the original issue on this thread it stopped. I'm still kind of convinced this is real though - I mean, if all of the example code leaked ports originally, I'm willing to believe that issue is real too, but just that most people don't create enough threads over time to hit it. Possibly some of the other code within the worker thread is leaking ports independently.

I was casually watching what other apps do wrt threads and ports - the one thing I noticed is that Safari creates and destroys a lot of threads (at least if you have as many windows open as I do), bu that it cleans them all up nicely after itself, so presumably there is a right way to do it (although I don't know whether Safari uses DO for that).


On 4 Dec 2006, at 17:57, j o a r wrote:


On 4 dec 2006, at 10.41, Martin Redington wrote:

I can't believe this is really the case - presumably DO is in fairly constant use, so surely this would have come up before now - but I can't work out what I'm doing wrong.

I don't think that DO is in much use in "serious" (ie. large and / or commercial) applications, so I wouldn't be surprised if bugs were to crop up.


Should I just expect some leakage?

No. If you can reproduce this problem in a consistent way, you should definitively file a bug report. This sound serious enough that it should be fixed pretty quickly.


j o a r



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: CFRunLookFindMode crash - revisited (From: Martin Redington <email@hidden>)
 >Re: CFRunLookFindMode crash - revisited (From: j o a r <email@hidden>)

  • Prev by Date: Re: 10.4 date format help
  • Next by Date: Re: 10.4 date format help
  • Previous by thread: Re: CFRunLookFindMode crash - revisited
  • Next by thread: Progressbar does not survive hide/show
  • Index(es):
    • Date
    • Thread