Are you saying that you can see the component on screen but the profiler doesn't show it in Live Objects?
Yes - I can see and interact with the component on-screen but in the Live Objects tab there is nothing there. I have also noticed that any other components nested within this component are not being displayed in the Live Objects tab.
Are all filters off?
Yes - everything is set to defaults. Just to reconfirm though, I can see the objects if creationPolicy is set to auto or not set at all, without changing any filters. As soon as I use creationPolicy="all", any components loading within the component that has creationPolicy set to all does not show in Live Objects.
Yeah, I know you said that. I was mostly hoping that maybe your code took a different code path when the creationPolicy is different and created some other class.
Is this a really big application? It is also possible that the profiler is running out of memory and creating all objects at startup is contributing to the problem.
FWIW, creationPolicy="all" is not a recommended configuration because of startup time impact and memory usage. It might be worth exploring ways of optimizing. If you are using the profiler, it is probably because you are facing a performance or memory issue and creationPolicy is going to be a factor.
I would look into ways of pre-instantiating a smaller subset of your views after startup. If you have a wizard/workflow app, just pre-instantiate the next view after the current view is up and running.