I have been having a lot of grief with FB 4.5 profiler failing on a socket connection where I am profiling an app that uses Parsley 2.4. Initially I thought the problem was related to some characterisitic of the application and/or the machine I am profiling from. However, I can across a bug opened on the Parsley 2.4 core.
Is the finger pointing at FB 4.5 accurate? If so, is there a fix available or planned?
Well, sort of. Flash Builder profiler will fail if there are too many objects to profile. Adding Parsley puts a load on the profiler, but so can any framework or tons of code.
IMHO, if FlashBuilder is failing (and you’ve tried to give it as much memory as you can) it is actually a sign that your app needs re-factoring so there aren’t as many objects around at any given time.