Flash Player 29.0.0.113 causing IE 11 on Windows 10 (64 bit) to hang and display "recover web page"

Hey, just wanted to follow up on this.  I was able to log in and poke around, but I was not able to reproduce the symptoms you're describing.  I followed up with a request for steps that might reproduce the problem, but didn't hear back.

My suspicion is that this is a product of specific GPO (Group Policy Object) settings that you've deployed to managed clients in your environment.

You could suss this out by trying to reproduce this on a stock Win10 image that doesn't have those GPOs applied (i.e. don't make it a member of your Windows domain).  If the issue doesn't reproduce there, then you can use the local policy editor to add your custom policies individually until you identify the culprit.

Other things I see with complex applications tend to come down to application logic issues.  A recent "escalation" had to do with an application where the company was basically loading their entire multi-gigabyte database into their application, instead of providing only windowed, relevant views of the data.  They were also using 32-bit browsers, and were hitting the 2GB per-process limit on addressable memory space. 

We see similar patterns a lot, where either applications are just loading ridiculous amounts of data (which is never used) into the client,  This has a huge impact on overall performance (consider garbage collection, where we have to walk a list of all of the instantiated objects to see what needs to be freed).

Alternatively, we frequently see scenarios where objects that get instantiated are never dereferenced, such that they *can* be freed by the garbage collector.  In that instance, the number of objects grows constantly as the application gets used, up until the process either runs out of memory, or where the number of managed objects just becomes so computationally expensive that the application grinds to a halt.

For those kinds of things, we provide a profiling tool called Adobe Scout, which would tell you useful things like "what's using all that memory?", "where's the application spending all of it's time?".   There are also some pathological situations in Flex where you can end up with the UI constantly resizing itself on every frame at specific screen resolutions and pixel depths due to floating point rounding errors and things.  If you see that the application is spending all of it's time in framework code, that's a pretty good indication that you need to look at those kinds of possibilities.  (Flex itself reached its end of life back in 2011, but we donated the code to Apache, and they've been updating it diligently for the last several years.  They're up to something like Flex 16 at this point, and as you can imagine, there have been more than a few bugfixes in that time.)