Anton Telyshev

Or ```go pprofMux := http.NewServeMux() pprofMux.HandleFunc("/debug/pprof/", pprof.Index) pprofMux.HandleFunc("/debug/pprof/cmdline", pprof.Cmdline) pprofMux.HandleFunc("/debug/pprof/profile", pprof.Profile) pprofMux.HandleFunc("/debug/pprof/symbol", pprof.Symbol) pprofMux.HandleFunc("/debug/pprof/trace", pprof.Trace) e.GET("/debug/pprof/*", echo.WrapHandler(pprofMux)) ```

[issue1312.zip](https://github.com/dominikh/go-tools/files/9356980/issue1312.zip)

+1

+1 I've opened a similar issue to gopdf: https://github.com/signintech/gopdf/issues/116 But later realized that the problem is not in leaks, but in the work of the application process.

Any news? 😢

https://github.com/jung-kurt/gofpdf/pull/321

+1

+1

+1

https://github.com/go-critic/go-critic/issues/1126