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
A crash sometimes occurs in the "ZPUino_VGA_Adapter/Demo" example code, because it can (depending on screen dimensions) pass out-of-bounds values to gfx.fillRect() and gfx.fillRoundRect() and this results in writing to memory outside the screen area.
It's subject to debate whether this should be fixed in library functions should fix this by checking their inputs (which may have a performance impact) or the "ZPUino_VGA_Adapter/Demo" example by avoiding the bogus values. Or both.
It doesn't always happen, it's one of those "Heisenbugs" which appear/disappear randomly as a result of any changes made in the code. I saw this bug on a Papilio Pro with 800x600 graphics after applying my own workaround to issue #24.
The text was updated successfully, but these errors were encountered:
A crash sometimes occurs in the "ZPUino_VGA_Adapter/Demo" example code, because it can (depending on screen dimensions) pass out-of-bounds values to gfx.fillRect() and gfx.fillRoundRect() and this results in writing to memory outside the screen area.
It's subject to debate whether this should be fixed in library functions should fix this by checking their inputs (which may have a performance impact) or the "ZPUino_VGA_Adapter/Demo" example by avoiding the bogus values. Or both.
It doesn't always happen, it's one of those "Heisenbugs" which appear/disappear randomly as a result of any changes made in the code. I saw this bug on a Papilio Pro with 800x600 graphics after applying my own workaround to issue #24.
The text was updated successfully, but these errors were encountered: