This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Quiet Pager · Radar

What changed in Go, Rust and Solidity this week.

What changed this week, from each project's own release notes, proposals and issues, with an exercise you can run for each change.

Written by a model · reviewed by a person · published Mondays · Atom feed

Archive · Week 36 · Aug 31 – Sep 6, 2026from 5 items

The Go team released point releases for both 1.26 and 1.27, tightening a handful of bugs in core packages. A new feature for profiling goroutine leaks was added to 1.27, giving developers a deeper view into runaway goroutines.

Worth knowingstdlib

Goroutine Leak Profiles

What changed
Go 1.27 includes new goroutine leak profiles.
Production impact
The source does not say.
Try it
Run go test -run TestLeak -benchmem -bench . on a program that intentionally leaks goroutines and observe the new profile output.
Source
go.dev/blog/goroutine-leak-profiles
Explain it

Understand it, then run it

Go 1.27 adds a new way to spot goroutine leaks in a running program. A goroutine leak happens when a goroutine blocks forever and the program can never unblock it. The new *goroutineleak* profile can be collected through the normal pprof HTTP endpoint, just like the usual goroutine profile. When you fetch that profile, it lists the goroutines that are permanently blocked on channels or sync primitives, making it easy to see where a leak is happening.

Exercise

Write a small program that starts a goroutine which never exits, then use the new goroutine leak profile to detect the leak.

The 60-second version

This week the Go team rolled out point releases for both 1.26 and 1.27, tightening a handful of bugs in core packages. They also added a new feature to Go 1.27: goroutine leak profiles. These profiles let you see exactly which goroutines are leaking and why, giving you a clearer picture when your application hangs or consumes too many resources. The releases include fixes across cgo, the compiler, the runtime, and several standard library packages, so upgrading to the latest point release is a good idea to stay on a stable, bug‑free foundation.

Written by gpt-oss-20b · claims checked against the sources · archive, not individually reviewed