We have a very large enterprise application with a small/medium memory leak. The last time we really profiled the app was when we, as developers, still all used Windows 7 and it all world swimmingly.
At that time we used a combination of the Flash Builder Profiler and Adobe Scout. Both gave useful information regarding the leak, but the ultimate find, last time was through the Flash Builder Profiler. Fast forward to today. We started using Scout and it's only getting us so far, so we'd like to use Flash Builder 4.7 Profiler. After much faffing around I managed to get it compiling again, I can run and debug the application (we hack the FlashPlayer debug version in to IE which works perfectly). However, when I try to run the Profiler it just fails to connect and times out. Has anyone had any luck using the Profiler in Windows 10? -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
