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

Jump to bottom

image/gif: image bounds obtained by image.Decode and gif.Decode are different #61519

Open
pic4xiu opened this issue Jul 22, 2023 · 2 comments
Open

image/gif: image bounds obtained by image.Decode and gif.Decode are different #61519

pic4xiu opened this issue Jul 22, 2023 · 2 comments
Labels
ExpertNeeded NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@pic4xiu
Copy link

pic4xiu commented Jul 22, 2023

What version of Go are you using (go version)?

❯ go version
go version go1.20.4 darwin/arm64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

macOS arm64

should have no effect

What did you do?

https://go.dev/play/p/f0RmDYbQALy

What did you expect to see?

outputs nothing because I want got and want to be the same

What did you see instead?

❯ go run main.go
(0,0)-(10,10) (48,0)-(58,10)
@pic4xiu pic4xiu changed the title affected/package: image/gif The image bounds obtained by image.Decode and gif.Decode are different: affected/package: image/gif Jul 22, 2023
@randall77
Copy link
Contributor

This is done intentionally here: https://cs.opensource.google/go/go/+/refs/tags/go1.20.6:src/image/gif/writer.go;l=462
CL that checked in that code: https://go-review.googlesource.com/c/go/+/9712
@nigeltao

@seankhliao seankhliao changed the title The image bounds obtained by image.Decode and gif.Decode are different: affected/package: image/gif image/gif: image bounds obtained by image.Decode and gif.Decode are different Jul 22, 2023
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 22, 2023
@bcmills bcmills added this to the Backlog milestone Jul 24, 2023
@aimuz
Copy link
Contributor

aimuz commented Nov 6, 2023

https://go.dev/play/p/CxdAlI5Yk62

In this way you will get consistent values

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ExpertNeeded NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
5 participants
@bcmills @randall77 @seankhliao @aimuz @pic4xiu