You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser Name and Version: Chrome Version 78.0.3904.108 (Official Build) (64-bit)
Operating System and version (desktop or mobile): Mac OSX 10.14.6
Expected Results
When the player reaches the end of a repeated segment, the cursor moves back to the start and plays the segment again however many times is specified in the AlphaTex
Observed Results
Player frequently does not repeat at all, and when it does it does not repeat the given number of times. There is also no indication above the repeat lines specifying how many times to repeat a given section.
In addition repeats can cause the renderer to use so much memory google chrome crashes. I see 150% CPU utilization when trying to render some AlphaTex with repeats
Steps to Reproduce (for bugs)
Using the sample AlphaTex provided for repeats, the first repeat does not happen, and the second repeat (set to repeat 3 times) only repeats once.
Your environment
Expected Results
When the player reaches the end of a repeated segment, the cursor moves back to the start and plays the segment again however many times is specified in the AlphaTex
Observed Results
Player frequently does not repeat at all, and when it does it does not repeat the given number of times. There is also no indication above the repeat lines specifying how many times to repeat a given section.
In addition repeats can cause the renderer to use so much memory google chrome crashes. I see 150% CPU utilization when trying to render some AlphaTex with repeats
Steps to Reproduce (for bugs)
Using the sample AlphaTex provided for repeats, the first repeat does not happen, and the second repeat (set to repeat 3 times) only repeats once.
Using the same AlphaTex above but changing the repeat amounts causes the memory/render issue which crashes Chrome
The text was updated successfully, but these errors were encountered: