Re: [go-nuts] Waitgroup.done wont Panic?

On Thu, May 14, 2020 at 8:18 AM sperberstephan via golang-nuts wrote: > Here: > https://play.golang.org/p/76AzuAiVGxL > > I thougt If the waitgroup gets below 0 there should be a Panic. > I understand that the goroutine is canceled. So maybe the defer Statement is > Not executed. > But why is the

[go-nuts] Waitgroup.done wont Panic?

Hi Folks, Here: https://play.golang.org/p/76AzuAiVGxL I thougt If the waitgroup gets below 0 there should be a Panic. I understand that the goroutine is canceled. So maybe the defer Statement is Not executed. But why is there No warning at the end of Main that some goroutines Had to be cancele

Re: [go-nuts] SetLang is not thread safe and memory leak

Thanks. Axel Wagner 于 2020年5月14日周四 04:13写道： > I'm afraid I don't understand the question. I guess you are referring to > this PR? > https://github.com/mylukin/easy-i18n/pull/2/files > It seems wrong in multiple ways (for starters, they change the module > path), but it also seems outdated; you h

[go-nuts] Getting cross-package test coverage data?

What's the current state of getting combined cross-package test coverage data? Specifically: - I have a lib directory containing my library code, which has some tests, but not many. - I have a cmd directory containing my main code and many tests that exercises the code in lib . -

Re: [go-nuts] Memory leak in github.com/golang/freetype

That is a very large dpi and size. The cache that is created is going to be very large. I am guessing that it allocates so much memory so fast that the process is killed by the OS Out of memory killer before the GC runs to free the “dead” faces. Thus the OOM death.. > On May 13, 2020, at 4:03 P

[go-nuts] Memory leak in github.com/golang/freetype

The following program using the freetype package leaks memory: https://play.golang.org/p/I90PYZUngVu The first two cycles have no problems but starting with the third cycle there is in an abnormal increase of CPU and memory usage. At the fourth cycle on my system the program is terminated by the

Re: [go-nuts] SetLang is not thread safe and memory leak

I'm afraid I don't understand the question. I guess you are referring to this PR? https://github.com/mylukin/easy-i18n/pull/2/files It seems wrong in multiple ways (for starters, they change the module path), but it also seems outdated; you have put several commits on master since then. >From a cas

[go-nuts] SetLang is not thread safe and memory leak

nevermind I missunderstood, my apologies. -- 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 on the

[go-nuts] SetLang is not thread safe and memory leak

My guess would be that whoever called Fprintf passed a nil, or uninitialized pointer as one of the variadic 'args' parameters, which holds interface{} type. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop

[go-nuts] SetLang is not thread safe and memory leak

I have just used golang for a month and I am not very familiar with this on. SetLang is not thread safe and memory leak？ https://github.com/mylukin/easy-i18n/blob/master/i18n/i18n.go#L43 Please expert guidance, and how to fix it? -- You received this message because you are subscribed to the G

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

Now you create your branch or whatever of the Go code and start porting it to your platform. As a first step, you will probably want to add the new nsx GOOS. Then you use your go1.14.2 installation to compile it (with bootstarp.sh) setting GOOS=nsx for cross compiling. Something like this: GOOS=ns

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

On Tuesday, 12 May 2020 20:02:01 UTC-4, Ian Lance Taylor wrote: > > On Tue, May 12, 2020 at 2:17 PM Randall Becker > wrote: > > > > On Tuesday, 12 May 2020 16:55:54 UTC-4, Ian Lance Taylor wrote: > >> > >> On Tue, May 12, 2020 at 1:11 PM Randall Becker > wrote: > >> > > >> > I have the g

[go-nuts] Re: sshagentca : project code review/security audit advice

FWIW, I put some thoughts around the wider security context of sshagentca (as opposed to hardening of the binary itself) in an issue in my own fork: https://github.com/candlerb/sshagentca/issues/8 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group.