Open
2 of 15 issues completedOpen
2 of 15 issues completed
Description
While we've found and fixed many gopls crashes thanks to telemetry, as we gain more users it appears we're accumulating a long tail of issues that "can't happen" based on easily verifiable local invariants.
In some cases, these were related to misreporting of stacks by the runtime (#70637), but others cannot be explained by a misreported stack, and indicate some form of memory corruption or (most likely) data race.
This issue is an umbrella for those bugs. @adonovan and I will consolidate them here.
Sub-issues
Sub-issues
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
- Manage this item control shift u
Metadata
Metadata
Assignees
Labels
Issues describing a possible bug in the Go implementation.This label describes issues relating to any tools in the x/tools repository.Issues related to the Go language server, gopls.Issues related to file corruption in gopls"can't happen" gopls crashes (races, unsafe, miscompile, runtime bugs, faulty HW)
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
14 remaining items
adonovan commentedon Mar 14, 2025
@findleyr Perhaps you could run gopls built with -race for a while? I've been doing it on my mac, but no problems so far.
adonovan commentedon Mar 18, 2025
The latest associated issue (#72931) is something new: