Skip to content

runtime: non-empty mark queue after concurrent mark [1.23 backport] #70323

Closed
@gopherbot

Description

@mknyszek requested issue #69803 to be considered for backport to the next 1.23 minor release.

@gopherbot Please open a backport issue for Go 1.23. This bug causes random crashes with no workaround for anything using the unique package, which includes applications using net/http.

Activity

added this to the Go1.23.4 milestone on Nov 13, 2024
gopherbot

gopherbot commented on Nov 13, 2024

@gopherbot
ContributorAuthor

Change https://go.dev/cl/627615 mentions this issue: [release-branch.go1.23] runtime: prevent weak->strong conversions during mark termination

added
CherryPickApprovedUsed during the release process for point releases
and removed
CherryPickCandidateUsed during the release process for point releases
on Nov 20, 2024
added a commit that references this issue on Nov 20, 2024
d8adc6c
gopherbot

gopherbot commented on Nov 20, 2024

@gopherbot
ContributorAuthor

Closed by merging CL 627615 (commit d8adc6c) to release-branch.go1.23.

added a commit that references this issue on Jan 28, 2025
0f31763
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    CherryPickApprovedUsed during the release process for point releasescompiler/runtimeIssues related to the Go compiler and/or runtime.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      runtime: non-empty mark queue after concurrent mark [1.23 backport] · Issue #70323 · golang/go