Running "test movie" command lags on Windows 10 build 19041.985
I am publishing to Air for Desktop and am having problems with "test movie" (crtl+enter). It seems to run frames really slowly. When I open scout to see what the problem is nearly all of the frame time is going to "other > other overhead". The strange thing is, this happens with any project, even a brand new one, and all versions of Air, but only if code is written in the timeline actions panel. Even a simple command like stop written on frame 1 with a completely empty project will cause this behavior, causing a 60fps project to run at ~25 fps.
If I publish the project everything runs fine, also if I enable detailed telemetry the "test movie" command works much better. I reported this bug to Adobe, but am wondering if anyone else is experiencing this.
