new issue address is https://github.com/golang/go/issues/17165
在 2016年9月20日星期二 UTC+8下午12:04:09，Ian Lance Taylor写道：
>
> On Mon, Sep 19, 2016 at 6:34 PM, Wanghb Wang > wrote:
> >
> >
> > 在 2016年9月20日星期二 UTC+8上午3:41:09，Ian Lance Taylor写道：
> >>
> >> On Mon, Sep 19, 2016 at 8:34 AM, Wanghb Wang
On Mon, Sep 19, 2016 at 6:34 PM, Wanghb Wang wrote:
>
>
> 在 2016年9月20日星期二 UTC+8上午3:41:09，Ian Lance Taylor写道：
>>
>> On Mon, Sep 19, 2016 at 8:34 AM, Wanghb Wang wrote:
>> >
>> > when I use stattcpupprof in my program, I got fatal error malloc
>> > deadlock.
>> > delete the cpu pprof, the program
在 2016年9月20日星期二 UTC+8上午3:41:09，Ian Lance Taylor写道：
>
> On Mon, Sep 19, 2016 at 8:34 AM, Wanghb Wang > wrote:
> >
> > when I use stattcpupprof in my program, I got fatal error malloc
> deadlock.
> > delete the cpu pprof, the program run well.
> >
> >
> > my question is :
> > Does startcp
On Mon, Sep 19, 2016 at 8:34 AM, Wanghb Wang wrote:
>
> when I use stattcpupprof in my program, I got fatal error malloc deadlock.
> delete the cpu pprof, the program run well.
>
>
> my question is :
> Does startcpuprof infect the malloc or resulting OOM Problem
I'm sorry, I don't understand the
when I use stattcpupprof in my program, I got fatal error malloc deadlock.
delete the cpu pprof, the program run well.
my question is :
Does startcpuprof infect the malloc or resulting OOM Problem
this is my panic stack trace:
fatal error: malloc deadlock
goroutine 17 [running, locked to threa
