A confusing and perhaps not that easily reconstructable observation, but... is it my imagination or a known issue but I've now seen a couple of times the strange issue of when there is a runtime error "soon enough" after startup, e.g. a call starting in the main application initialize() or the initialize() of the first view, you might end up with stacktraces that appear to originate from places that are never being called?
I did some refactoring where I removed a parameter from a constructor and got (correctly) a run-time error saying that there were too many parameters. But the stacktrace showed a class that I was only prototyping so it was never even instantiated in the application. And the second step was a class being used but not referencing the class where the problem actually was.
