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

runtime: "found bad pointer in Go heap" on solaris-amd64-oraclerel builder #37502

Open
bcmills opened this issue Feb 27, 2020 · 7 comments
Open

runtime: "found bad pointer in Go heap" on solaris-amd64-oraclerel builder #37502

bcmills opened this issue Feb 27, 2020 · 7 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Feb 27, 2020

2020-02-26T23:27:55-12cd55c/solaris-amd64-oraclerel

##### ../doc/codewalk
runtime: pointer 0xc00033c002 to unallocated span span.base()=0xc00033c000 span.limit=0xc00033dee0 span.state=0
runtime: found in object at *(0xc000230000+0x0)
object=0xc000230000 s.base()=0xc000230000 s.limit=0xc000232000 s.spanclass=10 s.elemsize=64 s.state=mSpanInUse
 *(object+0) = 0xc00033c002 <==
 *(object+8) = 0x9
 *(object+16) = 0xc00033c00e
 *(object+24) = 0x10
 *(object+32) = 0xc00033c021
 *(object+40) = 0xb
 *(object+48) = 0xc00033c02f
 *(object+56) = 0xc
fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)

The doc/codewalk test is pretty simple (no unsafe or cgo and only a little concurrency), so I suspect this is a runtime or platform bug.

Compare #35541, #32324, #28054.

CC @mknyszek, @cherrymui @aclements

@bcmills bcmills added this to the Backlog milestone Feb 27, 2020
@networkimprov

This comment has been minimized.

Copy link

@networkimprov networkimprov commented Feb 27, 2020

Also #37506

@bcmills

This comment has been minimized.

Copy link
Member Author

@bcmills bcmills commented Feb 27, 2020

@networkimprov, I don't think there is enough evidence on #37506 to suggest a link. (For all we know, that one really could just be incorrect use of unsafe or cgo.)

@dFionov

This comment was marked as off-topic.

Copy link

@dFionov dFionov commented Feb 27, 2020

@bcmills we don't use unsafe or cgo in application itself. It only used by thirdparties, like db-drivers. Also no problems with go 1.13...

@mengzhuo

This comment was marked as off-topic.

Copy link
Contributor

@mengzhuo mengzhuo commented Feb 28, 2020

@dFionov @networkimprov how is the page size of this builder?

@dFionov

This comment was marked as off-topic.

Copy link

@dFionov dFionov commented Feb 28, 2020

@mengzhuo could you clarify what do you mean? Are you talking about memory page size on build host? Do you need to compare it with page size on runtime?

@mengzhuo

This comment was marked as off-topic.

Copy link
Contributor

@mengzhuo mengzhuo commented Feb 28, 2020

@dFionov Yes, I mean system memory page size.
Go runtime has set the runtime page size to 8KB.
It's just my guess this issue is related to page size.

@dFionov

This comment was marked as off-topic.

Copy link

@dFionov dFionov commented Mar 2, 2020

@mengzhuo answered in #37506

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.