As I mentioned in my case, the images load fine when running through XCode, but not as a standalone binary. So, I guess the images themselves are fine. As producing an isolated test case scenario is going to be prohibitively difficult in my case, all I would like is a way to detect this happening so I can behave accordingly. Im my application, The "-11" errors start getting coughed up after a delay. Is there any way I can detect this error happening? My code that calls CGImageSourceCreateFromURL doesn't appear to produce null image sources, so I can't detect and handle this error condition.
Is there any way I can detect this error condition? -j On Fri, Aug 8, 2008 at 11:00 AM, Gary L. Wade <[EMAIL PROTECTED]> wrote: > I'd also try opening all the image files in some Apple-related graphics > programs (e.g., Preview, QuickTime Player, etc.) in order to determine if > it's system-wide or some combination in your own application; of course, > there are other factors that would be involved in using these, but since > Apple software also relies upon OS-level technologies, if it happened there, > it'll help Apple track down the bug. > > Nevertheless, it sounds like you're going to have to produce a small > application along with any particular combination of image files that can > reproduce the problem and submit it as a bug. If you've got a DTS incident > available, you probably should forward them the bug number to expedite things. > > According to a MacNN article this morning: > > http://www.macnn.com/articles/08/08/08/new.mac.os.x.1055.build/ > > if you've got a developer seed key, you might try that out to see if a bug > related to this is fixed. And, if there is a 10.5.5 coming out (whether or > not there is, I can't say so), getting this submitted through the DTS channel > today, if it's an OS-level thing, might get you the fix you need more quickly. > >>Well, I can't speak for James, but I have forced the thumbnail >>creation to have at most 10 files opened at the same time, and it >>doesn't make a difference... >>I could understand a memory allocation issue, if the app didn't take >>roughly 100 megs of RAM. >>And besides, I can see there's a difference between running in debug >>and release mode too... >> >>Does anyone know what -11 means? Let's forget for a minute how we do >>things, I guess James and I don't have the same app, the same goals >>and the same method of getting the images... >>If the lib explicitely indicates that it's a -11 error, maybe there's >>a simple explanation? >> >>On 06 Aug 2008, at 23:36, Gary L. Wade wrote: >> >>> Off the top of my head, with a number of files being opened so high >>> and relatively close to the value you get from getrlimit with a >>> parameter of RLIMIT_NOFILE, I'd suggest checking to see if that's >>> the problem. >> >>-- >>Zino > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please 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: > http://lists.apple.com/mailman/options/cocoa-dev/trankelson%40gmail.com > > This email sent to [EMAIL PROTECTED] > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
