Panic in case of the request has been processed

[aryanmehrotra]

Describe the bug
I created a goroutine which would panic after 10 seconds after request came, and then it would panic.

To Reproduce
Sample Handler code

func HelloHandler(c *gofr.Context) (any, error) {

	go func() {
		time.Sleep(10 * time.Second)

		panic("i panicked after 10 seconds")
	}()

	name := c.Param("name")
	if name == "" {
		c.Log("Name came empty")
		name = "World"
	}

	return fmt.Sprintf("Hello %s!", name), nil
}

Expected behavior
App should not crash

Screenshots

[coolwednesday]

Hey @aryanmehrotra,

This is expected behavior in Go:
Panic recovery in net/http or using middleware only works for panics in the main handler goroutine. If you start a new goroutine inside your handler and it panics, recovery middleware cannot catch it—this will crash your whole app unless you handle the panic inside that goroutine.

Many web frameworks (Echo, Gin, Chi, Fiber) provide recover middleware that allows you to customize the logging and error response when a handler panics, but the mechanism remains the same: the recovery only handles panics that happen in the handler goroutine itself, not in any goroutine spawned by the handler

Reason:
Each goroutine in Go is completely independent; there’s no hierarchy or parent-child relationship between goroutines. Because of this, recovery must happen inside the exact goroutine where the panic might occur; middleware can’t help here.

How to fix:
Wrap your goroutine function with a deferred recover, like:

go func() {
    defer func() {
        if r := recover(); r != nil {
            // handle or log the panic here
        }
    }()
    // your goroutine work here
}()

Or use a helper:

func SafeGo(fn func()) {
    go func() {
        defer func() {
            if r := recover(); r != nil {
                log.Printf("goroutine panic: %v", r)
            }
        }()
        fn()
    }()
}

and then call:

SafeGo(func() {
    // your work here
})

Summary:
Always recover from panics inside each goroutine. Because goroutines are independent, HTTP middleware cannot recover these panics for you.