golang/go

internal/chacha8rand: unrecognized failures

Open

#77064 opened on Jan 4, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
NeedsInvestigationarch-mipscompiler/runtimehelp wanted

Description

#!watchflakes
default <- pkg == "internal/chacha8rand" && test == ""

Issue created automatically to collect these failures.

Example (log):

FAIL	internal/chacha8rand [build failed]
# reflect [internal/chacha8rand.test]
SIGSEGV: segmentation violation
PC=0xae0c4 m=4 sigcode=128 addr=0x0

goroutine 0 gp=0xffa89ac1c0 m=4 mp=0xffa89a8008 [idle]:
runtime.goschedImpl(0xffa89301c0, 0x1)
	runtime/proc.go:4325 +0x114 fp=0xffa89bfe98 sp=0xffa89bfe48 pc=0xae0c4
runtime.gopreempt_m(...)
	runtime/proc.go:4362
...
r16  0x40	r17  0x698cf698cf698cf6
r18  0xffffffffffff	r19  0x6779ccb00cfc1915
r20  0x6a3e7cf96f4e121a	r21  0xf4e869294fd02579
r22  0x0	r23  0xffffffffffffefff
r24  0xdeb3c84b1c2c6e4b	r25  0x44dd24f091a8bcf0
r26  0x0	r27  0x0
r28  0x0	r29  0xffa89bfe48
r30  0xffa89ac1c0	r31  0xc9548
pc   0xae0c4	link 0xc9548
lo   0x0	hi   0x0

— watchflakes

Contributor guide

Tech stack
go
Domain
backendperformance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go runtime understandingAssembly debuggingSignal handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Examine the segmentation violation in internal/chacha8rand test. The stack trace shows a SIGSEGV in runtime.goschedImpl. Investigate the PC=0xae0c4 and register values to identify memory corruption. Check recent changes to chacha8rand assembly or runtime scheduler. Look at the build log for more details.