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
The following example causes a segfault (Python 3.12.5, pygame-ce 2.5.1):
importpygamesurf=pygame.Surface( (315,271), depth=24 )
#Crash on following line:pygame.draw.aaline( surf, (255,0,255), (100,207),(20,229) )
Some coordinates can be passed safely, while others cannot. When it works, it seems to draw a line with the correct locations, but blended incorrectly. Meanwhile, 32-bit surfaces do not have this problem. This tells me that this function is not respecting the pixel stride.
The text was updated successfully, but these errors were encountered:
damusss
added
draw
pygame.draw
segfault
For PRs that fix segfaults or issues containing segfaults which have an higher priority
labels
Aug 21, 2024
Thanks for the report ! This is something we're already aware and I'm currently working on a fix, which should be available in the next pygame-ce version.
The following example causes a segfault (Python 3.12.5, pygame-ce 2.5.1):
Some coordinates can be passed safely, while others cannot. When it works, it seems to draw a line with the correct locations, but blended incorrectly. Meanwhile, 32-bit surfaces do not have this problem. This tells me that this function is not respecting the pixel stride.
The text was updated successfully, but these errors were encountered: