The problem, as I remember it, stemmed from anything based on the YUI Container collection. It’s not a bug or a problem in its own right, but when you create a zillion of them, the construction overhead really adds up.

Since I wrote this article, Firebug 1.0 betas have become available and they have [very nice] profiling support, too. To tackle this problem, I’d recommend using Firebug’s stack trace functionality. Modify the YAHOO code to include a call to console.trace() in whichever function is giving you grief, then run your application normally. Check the Firebug console and you’ll have a ton of debug output. It will take some work, but you can pore over that to figure out what’s making all those zillions of calls.

Hope that helps!

Can you elaborate a bit on the problem you found with YUI’s CustomEvent? I, too, am finding extraneous calls being made to CustomEvent, although we’re not using Tooltip.

I’d appreciate any insight you can offer, as I’m sure we’re suffering a similar issue.

Thanks.

http://www.softwareverify.com

Proper profiler - no JavaScript wrappers. All timing handled by C code. Runtime
callstack display, tabular statistics, relations view, call tree, call graph, analysis feature,
HTML/XML export etc, etc. Uses the same profiling APIs that Venkman uses.

Works with Firefox 1.0, 1.5, 2.0 and Flock 0.7

Disclaimer - I was involved in the design of JSPV (Object Media consult for Software Verification).

Stephen

great article.