Today I installed FB 4.7 on my personal Windows 10 computer. I have the
debugger version of FP32 in an older FIreFox (v47). The profiler worked for me.
HTH,
-Alex
On 2/28/19, 1:32 AM, "DarrenEvans" <darren.ev...@allocatesoftware.com> wrote:
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:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C3ebae5c97a30491a8ef608d69d5f9739%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636869431212051651&sdata=NRdXtXtnbNPqn6kJ1mL1eKOis4NnvQMAIuDiokL5EDM%3D&reserved=0
