IKImageBrowserView is known to support something like 250,000 images
so I'd look somewhere else.
Providing the full crash stack trace might help understand what object
you (or some other place) is likely to be over-released.
Also, enabling NSZombie might help you debugging the problem.
--
Julien
Sent from my iPhone
Le 7 mars 08 à 22:34, Scott.D.R <email@hidden> a
écrit :
Greetings everyone.
As the title mentioned, I am using the IKImageBrowserView to provide
a quick preview of many pictures.
However, I found my application regularly crashed. The GDB outputs
complained it met something like:
"IKImagedatabase CFHash..." and so on.
It seems that it is related to the image kit database hash problem.
From which we can image the problem may come from the huge number of
pictures(approximately over 3,000).
Finally, I reduced the picture number to 2500, 2000, 1500, 1000 ...
350 ... 250. The problem continued. At last, I provided it with 100.
Thanks to god, the GDB finally got quiet.
So I am wondering whether there exists some top limit for the number
of pictures to be displayed with IKImageBrowserView?
Thank you very much for any reply.
Best regards.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
