\"Failcase\" is, for example, the Table View Layout 2 test in\nKitchenSink. It's not really a \"failure\" since the test actually\nworks. But behind the scenes a bunch of exceptions -- handled\nexceptions -- are happening, very likely affecting performance.
\nYou can see it happening if you run KS with <property\ntype=\"bool\" name=\"ti.android.debug\">true</property>\nin tiapp.xml. Run adb logcat at the command line, then\n-- with KS running in your emulator -- go to the Views -> Table\nViews -> Layout 2 test. As the test loads, watch logcat\nscrolling by -- you'll end up seeing a ton of exceptions. If you\nthen scroll up and down on the table view in the test, you'll see a\nton more exceptions being logged in logcat.
Alternatively, you can watch me doing it here:
\nhttp://screencast.com/t/FD9E6klYe
\nWhat's happening is this: Because the image path begins with\nResources/images -- which is one of our standard locations to check\nfor density-specific images -- we do the density image name\nmangling and check to see if the image exists as an Android\nresource. The checking to see if it's a resource uses reflection\n(see TiRHelper.locateResource), and has to accept the\nfact that an exception will be raised if the resource doesn't\nexist. It handles that fine (and sends it to logcat if debug is\nturned on -- which is what we're seeing in that video) and the\nresult is that our loadDrawable method ends up\nsuccessfully finding the image file in the standard file system.\nBut I imagine those exceptions are expensive. The problem is that\n-- unlike successful finds of a resource image -- we do\nnot cache the failures. So it tries every\ntime to load the same image as a resource that doesn't\nexist.
I think putting images into the Resources/images folder is\nprobably a fairly common pattern for app developers. So we could\nperhaps improvement performance for these people by caching\nresource lookup failures to avoid going through the series of\nexceptions over and over again.
(from [b47d085bb43a5bc9b885ee89d7067eddccbbc8db])\nWhen looking up Resource/android/images/xxx images in the android\nresources, don't bother checking for android system resources,\nsince by definition you're looking for a project-specific resource.\nSaves one lookup. [#3040] \nhttps://github.com/appcelerator/titanium_mobile/commit/b47d085bb43a...
Hmm, as usual one of my commits not listed automatically. The\nmain commit for this item is:
\n\nhttps://github.com/appcelerator/titanium_mobile/commit/e7beec84f520...
QE Testing: follow the elaborate :) instructions up in the\ndescription, and (in the pre-fix version of the SDK) you'll see a\nbunch of exceptions scrolling by in logcat (they will be\ncategorized as \"TiRHelper\"). Then, after installing the fixed\nversion, you won't see those exceptions anymore.