Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when resampling image (probably very similar to #529, but persisting) #580

Open
Sototoki opened this issue May 18, 2024 · 2 comments
Labels

Comments

@Sototoki
Copy link

Crash when resampling image (probably very similar to #529, but persisting )

2 reproduce:
-Open Lazpaint (7.2.2 64 bit) on MX-Linux (MX-21.3_ahs_x64 newest updates)
(bug not new, known for surely 2 y)
( Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: loaded: N/A
unloaded: fbdev display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") )

-click on toolbar "Floodfill"
-click on canvas, so that it will be filled
-click menu Image/Resample, so that dialog opens
( aspect ratio is checked and unit is set to pixel when opening)
-click on upper arrow button of width
-click OK
---> LazPaint evaporating


when started from cli, there, after crashing:
$ lazpaint
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$0000000000000000
$0000000000647074
$000000000044AD48
$000000000044A9F9
$000000000044B11D
$0000000000646A43
$000000000044B06F
[FORMS.PP] ExceptionOccurred

@circular17
Copy link
Collaborator

Hello Sototoki!

Thanks for letting me know about the bug.

Have you tried the fixed version proposed in the discussion of #529 ?
https://github.com/bgrabitmap/lazpaint/releases/download/v7.2.2/lazpaint7.2.2_linux64_qt5_bugfix.tar.gz

Regards

@circular17 circular17 changed the title Crash when resampling image (probably very similar to #529, but persisting ) Crash when resampling image (probably very similar to #529, but persisting) May 26, 2024
@circular17
Copy link
Collaborator

I'm planning a new release. So the fix for #529 will be included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants