[
https://issues.apache.org/jira/browse/BEAM-14237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527484#comment-17527484
]
Maksim Gaiduk commented on BEAM-14237:
--------------------------------------
Sorry for a pause on my side.
I've rewrote the script a bit to make it more obvious what the problem could
be: [https://pastebin.com/raw/4aF8UrRu]
By doing so, I've actually managed to catch sigsegv on my machine:
[https://pastebin.com/raw/S5BT9C9f]
I am not sure if it is a hardware problem, I will try to reproduce the same bug
on several of M1 macs and see what happens
> Golang Beam ParDo job not working as expected on Apple M1 chip
> --------------------------------------------------------------
>
> Key: BEAM-14237
> URL: https://issues.apache.org/jira/browse/BEAM-14237
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Affects Versions: 2.37.0
> Reporter: Maksim Gaiduk
> Assignee: Jack McCluskey
> Priority: P2
>
> Reproducible example:
> reproducible.go: [https://pastebin.com/raw/LqADath4]
> go.mod: [https://pastebin.com/raw/qXmyh62N]
> run cmd: go run reproducible.go --output output.tsv
> On lines 29-31, the program is supposed to read from rowIter function only
> while new data is available (this is standard interface to read input after
> GroupBy operation).
> Instead, the cycle runs indefinitely. In gdb/debug prints it can be clearly
> seen that program just steps through the "if !b" block when "b" is false.
> Supposedly this is the cause of UB from ABI function call inside beam.
>
> Go version: go1.18 darwin/arm64
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
