[go-nuts] Re: Short destination error with unicode.Transform

Update after seeing the error again. I inlined everything, creating the transformer on every invocation, to avoid any races, but the error persists. https://gist.github.com/jschaf/bd600ce71ad3798af6c160d74904ac9c I'm unable to reproduce the error locally. My current plan is to attempt to worka

[go-nuts] Re: [golang-dev] Go 1.20 Release Candidate 3 is released

Hi gophers, This is a small RC that primarily includes the latest fix for https://go.dev/issue/56784, crashes while running processes with os/exec on macOS and iOS. All testing is always welcome, but we're particularly interested in that bug. Thanks, Heschi for the Go team On Thu, Jan 12, 2023 a

Re: [go-nuts] Re: Design patterns. builder ?

Hi All ! In case some one is in interest of the builder patterm industrial implementation. So, I have found that there are a very intresting use the package named https://github.com/spf13/cobra. The package should be considered In context of the builder pattern implementation for realizaton of

[go-nuts] Go 1.20 Release Candidate 3 is released

Hello gophers, We have just released go1.20rc3, a release candidate version of Go 1.20. It is cut from release-branch.go1.20 at the revision tagged go1.20rc3. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Re

[go-nuts] Re: Automation with the ultimate guide to GO language

"Although the official logo has two capital letters, the language name is written Go, not GO." https://go.dev/doc/faq#go_or_golang On Wednesday, January 11, 2023 at 9:27:46 PM UTC+1 ashwin...@gmail.com wrote: > Unlock the full potential of automation with the

Re: [go-nuts] Re: Debugging memory leak when a GO process crashed

You can certainly have memory leaks in Go - due to undesired references retaining the object. What the op is asking for is a memory dump at OOM crash. If the dump shows 1M object X and the author believes there should only be 1 - you have a leak > On Jan 12, 2023, at 4:01 AM, mariappan balr

Re: [go-nuts] Re: Debugging memory leak when a GO process crashed

Hi Brian, A Go program can crash because of Out of Memory. Yes it can be because of goroutine leak. Or it can have some reference to global variables, but it should be freed? How to debug this? When the leak is happening while using CGO, is there any tool to debug this? Best Regards Mariappan On

[go-nuts] Re: Debugging memory leak when a GO process crashed

I think you're not being clear on your problem you're trying to solve. There are no "memory leaks" in Go in the traditional sense (omitting to free an allocation) because of the garbage collector. Therefore, if memory is not being freed in a pure Go program, it's because you are keeping a refer