AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: go-chi-zero-allocation-context-lifecycle-guardrail

Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention

Enforces strict context decoupling and allocation controls when routing with go-chi/chi/v5 in ultra-high-throughput Go microservices. Prevents severe data races and memory contamination stemming from chi's internal sync.Pool context reuse when goroutines outlive the HTTP request lifecycle.

Prohibited Anti-Pattern: Retaining or Spawning Goroutines with Raw Chi Request Context Causing sync.Pool Data Race and Memory Contamination

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention - Enforces strict context decoupling and allocation controls when routing with go-chi/chi/v5 in ultra-high-throughput Go microservices. Prevents severe data races and memory contamination stemming from chi's internal sync.Pool context reuse when goroutines outlive the HTTP request lifecycle.
globs: **/*.go
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/go-chi-zero-allocation-context-lifecycle-guardrail"
---

# Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Retaining or Spawning Goroutines with Raw Chi Request Context Causing sync.Pool Data Race and Memory Contamination

## System Constraints
You are a Principal Go Architect and Systems Engineer enforcing absolute memory safety and zero-pollution context lifecycles in go-chi/chi/v5 services. Chi reuses its internal chi.Context instances via sync.Pool. Passing chi.Context directly into asynchronous goroutines or failing to detach standard request contexts leads to silent cross-request data leaks, route corruption, and severe memory races. Mandate strict context dissociation and bounded allocations.

## Strict Guidelines
- Engineers MUST NEVER pass raw r.Context() directly to detached or background goroutines launched inside a Chi handler.
- Engineers MUST ALWAYS clone values and create a decoupled context using context.WithoutCancel(r.Context()) (Go 1.21+) or construct a fresh context.Background() populated only with explicitly copied metadata for background processing.
- Engineers MUST NEVER mutate chi.RouteContext(r.Context()) directly inside application handlers or shared middleware unless operating within a custom terminal router pass.
- Engineers MUST explicitly extract needed URL params via chi.URLParam(r, key) and copy primitive strings before delegating work to any asynchronous queue or processing pool.
- Engineers MUST NOT store stateful heap-allocated structs directly into request context without utilizing statically typed wrapper keys to avoid GC write-barrier thrashing.
- Code SHOULD verify concurrent execution safety across HTTP boundaries with Go race detection (-race) in automated integration test pipelines.

## Bad vs Good Implementations
### Asynchronous Goroutine Execution Spawning from Chi Context

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Chi recycles chi.Context via internal sync.Pool on handler completion. Passing r.Context() to an asynchronous goroutine causes data races when Chi zeroes out the internal RouteContext while the goroutine is still reading it.
```go
package handlers

import (
	"net/http"
	"github.com/go-chi/chi/v5"
)

func AsyncAuditHandler(w http.ResponseWriter, r *http.Request) {
	userID := chi.URLParam(r, "userId")
	// CRITICAL BUG: r.Context() holds Chi's pooled *chi.Context.
	// When this handler returns, Chi resets and returns the RouteContext to sync.Pool.
	// The async goroutine experiences severe data races and cross-request context poisoning.
	go func() {
		ProcessAuditLog(r.Context(), userID)
	}()
	w.WriteHeader(http.StatusAccepted)
}

func ProcessAuditLog(ctx interface{}, id string) {}
```

#### Production Standard (Correct)
> **Standard**: By decoupling the context via context.WithoutCancel (or a freshly initialized background context) and isolating primitive route parameters via string cloning, the async task safely executes independent of Chi's sync.Pool lifecycle.
```go
package handlers

import (
	"context"
	"net/http"
	"strings"
	"github.com/go-chi/chi/v5"
)

func AsyncAuditHandler(w http.ResponseWriter, r *http.Request) {
	// Explicitly extract and clone the primitive string value
	userID := strings.Clone(chi.URLParam(r, "userId"))

	// Decouple cancellation and remove Chi's pooled RouteContext lifecycle
	// Go 1.21+ context.WithoutCancel preserves request values while severing cancellation,
	// or context.Background() can be used with explicit trace context propagation.
	asynCtx := context.WithoutCancel(r.Context())

	go func(ctx context.Context, id string) {
		ProcessAuditLog(ctx, id)
	}(asynCtx, userID)

	w.WriteHeader(http.StatusAccepted)
}

func ProcessAuditLog(ctx context.Context, id string) {}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

GolangCI Lint Inspector MCP
Analyzes Go source trees for concurrency bugs, context leakage, and improper goroutine lifecycles using static linters.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Go Race Detector & Vet Runner
Executes Go test suites with -race and -gcflags='-m' to identify heap allocations and pool race conditions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention

Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention defines an industrial-grade behavioral standard for backend engineering. Enforces strict context decoupling and allocation controls when routing with go-chi/chi/v5 in ultra-high-throughput Go microservices. Prevents severe data races and memory contamination stemming from chi's internal sync.Pool context reuse when goroutines outlive the HTTP request lifecycle. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Retaining or Spawning Goroutines with Raw Chi Request Context Causing sync.Pool Data Race and Memory Contamination Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftRetaining or Spawning Goroutines with Raw Chi Request Context Causing sync.Pool Data Race and Memory ContaminationCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST NEVER pass raw r.Context() directly to detached or background goroutines launched inside a Chi handler.

Engineers MUST NEVER pass raw r.Context() directly to detached or background goroutines launched inside a Chi handler.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST ALWAYS clone values and create a decoupled context using context.WithoutCancel(r.Context()) (Go 1.21+) or construct a fresh context.Background() populated only with explicitly copied metadata for background processing.

Engineers MUST ALWAYS clone values and create a decoupled context using context.WithoutCancel(r.Context()) (Go 1.21+) or construct a fresh context.Background() populated only with explicitly copied metadata for background processing.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST NEVER mutate chi.RouteContext(r.Context()) directly inside application handlers or shared middleware unless operating within a custom terminal router pass.

Engineers MUST NEVER mutate chi.RouteContext(r.Context()) directly inside application handlers or shared middleware unless operating within a custom terminal router pass.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Engineers MUST explicitly extract needed URL params via chi.URLParam(r, key) and copy primitive strings before delegating work to any asynchronous queue or processing pool.

Engineers MUST explicitly extract needed URL params via chi.URLParam(r, key) and copy primitive strings before delegating work to any asynchronous queue or processing pool.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Engineers MUST NOT store stateful heap-allocated structs directly into request context without utilizing statically typed wrapper keys to avoid GC write-barrier thrashing.

Engineers MUST NOT store stateful heap-allocated structs directly into request context without utilizing statically typed wrapper keys to avoid GC write-barrier thrashing.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Code SHOULD verify concurrent execution safety across HTTP boundaries with Go race detection (-race) in automated integration test pipelines.

Code SHOULD verify concurrent execution safety across HTTP boundaries with Go race detection (-race) in automated integration test pipelines.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Go Chi Context Lifecycle and sync.Pool Cross-Request Memory Leak Prevention critical for AI coding assistants?

Enforces strict context decoupling and allocation controls when routing with go-chi/chi/v5 in ultra-high-throughput Go microservices. Prevents severe data races and memory contamination stemming from chi's internal sync.Pool context reuse when goroutines outlive the HTTP request lifecycle. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Retaining or Spawning Goroutines with Raw Chi Request Context Causing sync.Pool Data Race and Memory Contamination) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Go