golang/go

x/net/html: TestComments failed due to SEGV in runtime.runqgrab [mips64le]

Open

#77185 opened on Jan 15, 2026

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

Description

#!watchflakes
default <- pkg == "golang.org/x/net/html" && test == "TestComments"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestComments
SIGSEGV: segmentation violation
PC=0x7a490 m=4 sigcode=1 addr=0x0

goroutine 0 gp=0xc000003500 m=4 mp=0xc000047808 [idle]:
runtime.runqgrab(0x0, 0xc000030698, 0xb, 0x0)
	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:6993 +0x40 fp=0xc00007bd08 sp=0xc00007bcf0 pc=0x7a490
runtime.runqsteal(0xc000030508, 0x0, 0x0)
	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:7048 +0x64 fp=0xc00007bd40 sp=0xc00007bd08 pc=0x7a6f4
runtime.stealWork(0xc24e6b1a4bd)
...
r16  0x1	r17  0xc000047808
r18  0x0	r19  0x6001
r20  0x30008	r21  0x6b01db030f07405d
r22  0x23b488	r23  0x380000
r24  0x823300858031f705	r25  0xfffeb88360
r26  0x0	r27  0x0
r28  0x0	r29  0xc00007bcf0
r30  0xc000003500	r31  0x7a6f4
pc   0x7a490	link 0x7a6f4
lo   0x0	hi   0x3

— watchflakes

Contributor guide

Tech stack
go
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
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.
clear
Prerequisites
Go runtime internalsmips64le architecturedebugging SEGVscheduler knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
5
Research direction
Investigate the segmentation violation in runtime.runqgrab on mips64le architecture. The crash occurs at proc.go:6993 in the function runqgrab. Review the Go runtime source code for that function and check for architecture specific issues. Look into whether there are prior reports or fixes for mips64le scheduler problems. Attempt to reproduce the failure on a mips64le system or emulator.