Excellent. Congrats!! Regards,
Andreas
On 18/06/2016, at 14:25, Christiaan Hofman
<cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote:
On Jun 17, 2016, at 16:40, Christiaan Hofman
<cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote:
I can finally see the crasher myself now, as I have finally upgraded to 10.11.
So this again shows this is at least partly an OS bug, as it seems o occur only
in 10.9 and 10.11, and not in 10.10.
I also tried my proposal to use (a finite number of) non-releasing controllers
as the web view delegates. But unfortunately this did not fix the problem. So
perhaps it’s not related to the web view delegate.
One thing I noted is that the crash happens after a little while, and does not
occur if the max number of web views is large enough for all web view icons.
This makes me now suspect that the problem has to do with the notification.
Also because in your tests the strange retainCount jumps happen around those
notifications. So perhaps there’s something off with the timing of those
notifications. Perhaps it has to do with the fact that several icons are
notified at once, even though only one web view will be available, so that may
perhaps get some run condition between the waiting icons?
One thing that seems wrong to me in the code is the main thread check in
-[FVWebViewIcon release]. Should that not be pthread_main_np() == 0 rather than
!= 0? Not that changing this fixes the crasher.
Christiaan
I think I finally fixed the problem!
It looks like the web view is a complete red herring. The problem is with the
notification center. Apparently there is something fishy going on with how
NSNotification references the object. I have replaced the notification center
by a simply non-retaining array to hold the icons waiting for rendering. I’ve
seen no crashes since!
Christiaan
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.
http://sdm.link/zohomanageengine_______________________________________________
Bibdesk-develop mailing list
Bibdesk-develop@lists.sourceforge.net<mailto:Bibdesk-develop@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Bibdesk-develop mailing list
Bibdesk-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
