Flash player cpu usage with WGT games

Question

The system...Macbook pro13 inch  mid-2012osx el capitan 10.11.32.5 ghz intel core i516 gb 1600 mhz ddr3 ramintel hd graphics 4000 1536 mbSafari version 9.0.3 (11601.4.4)NPAPI Plug-in version 21.0.0.197 is installed.PPAPI Plug-in version 21.0.0.197 is installed.Comcast internet broadband benchmarked at 155 Mbps download, 12 Mbps upload speeds.Unfortunately, I’m not able to directly connect to the modem.  I use a wireless home network.  Apple Time Machine, or a wireless extension Apple Airport Express.Here’s the issue-When playing WGT (World Golf Tour) games, it will play normally for a certain period of time.  Watching the Activity Monitor will show the Flash Player as the most active process, and when running normally will use around 50% cpu power.  At random times, usually when trying to animate the set up to a very long putt, the Flash player will start grabbing anywhere from 150% to 175% cpu power.  This will cause the animation to break down completely.  It will stutter and lag, and click response will be nonexistent, making gameplay impossible.  The simple solution to this is to reload the page when you start to see cpu usage climbing.  This will take care of the problem momentarily, as long as you are playing a solo game.  The problem with this solution is that one type of gameplay can be with multiple players online playing the same course together, and your team is only allowed to disconnect from the game three times before being forced to forfeit the match.  As long as you are not playing for money, that’s fine, though annoying.  This has only been a major problem on my system since the early part of this year with the updates to Flash, but uninstalling and going back to previous versions of Flash did not solve the problem either.  It has always been a problem to some degree.  I’m wondering what is causing the massive rise in Flash player cpu usage at random times, because sometimes it handles the load just fine.

jeromiec83223024 · Answer

Flash Player is a language runtime. We process ActionScript written by the content provider, and do all the nuts-and-bolts stuff, like allocating memory and rendering pixels to the screen. Game developers often times push the edge of what's possible with Flash, and don't always write the most efficient code.

We make a performance profiling tool available for content developers called Adobe Scout that allows them to track what code is spending the most time on various activities, so that they can identify and optimize hotspots.

It's unlikely that there's a generic fix that we can make that will magically improve performance for this one game. The best course of action is to report the performance issue to the game developer, and encourage them to profile it using Scout. If they identify a specific problem with an ActionScript call that's super slow or something, they'll be able to isolate that case and ask us the fine-grained technical question necessary to either identify an actionable problem, or provide them with a recommendation on a better approach, etc.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.