In fact the code you reference - the close() - does things the Go docs warn specifically not to do. You may be better off using runtime.AddCleanup() On Mar 19, 2025, at 6:32 AM, Robert Engels <reng...@ix.netcom.com> wrote: -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/06F75F94-7947-4A97-98EA-DB1B6A47C8E8%40ix.netcom.com. |
- Re: [go-nuts] Memory leak from sqlite3 l... robert engels
- Re: [go-nuts] Memory leak from sqli... 'Michael Knyszek' via golang-nuts
- Re: [go-nuts] Memory leak from ... Robert Engels
- Re: [go-nuts] Memory leak f... Elad Gavra
- Re: [go-nuts] Memory le... Robert Engels
- Re: [go-nuts] Memo... Gavra
- Re: [go-nuts] ... 'Brian Candler' via golang-nuts
- Re: [go-nu... Gavra
- Re: [go-nuts] Memory leak from sqli... Robert Engels
- Re: [go-nuts] Memory leak from ... Gavra
- Re: [go-nuts] Memory leak f... 'Michael Pratt' via golang-nuts
- Re: [go-nuts] Memory leak f... Robert Engels
- Re: [go-nuts] Memory le... Gavra
- Re: [go-nuts] Memo... 'Michael Knyszek' via golang-nuts
- Re: [go-nuts] ... 'Michael Knyszek' via golang-nuts
- Re: [go-nu... Gavra
- Re: [go-nu... 'Michael Knyszek' via golang-nuts