[Go - Note] Channel 阻塞deadlock和panic情况,以及close channel
Arboat · · 1328 次点击 · · 开始浏览阻塞:
发生一直阻塞时,会报如下deadlock错误:
fatal error: all goroutines are asleep - deadlock!无缓存channel:
- 通道中无数据,但执行读通道。
- 通道中无数据,向通道写数据,但无协程读取。
有缓存channel:
- 通道的缓存无数据,但执行读通道。
- 通道的缓存已经占满,向通道写数据,但无协程读。
Panic:
1.向已经关闭的channel写。
2.关闭已经关闭的channel。
close channel:
You needn't close every channel when you've finished with it.It's only necessary to close a channel when it is important to tell the receiving goroutines that all data have been sent.
Note that it is only necessary to close a channel if the receiver is looking for a close. Closing the channel is a control signal on the channel indicating that no more data follows.
It's OK to leave a Go channel open forever and never close it. When the channel is no longer used, it will be garbage collected.
有疑问加站长微信联系(非本文作者)
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
关注微信- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码` - 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传
收入到我管理的专栏 新建专栏
阻塞:
发生一直阻塞时,会报如下deadlock错误:
fatal error: all goroutines are asleep - deadlock!无缓存channel:
- 通道中无数据,但执行读通道。
- 通道中无数据,向通道写数据,但无协程读取。
有缓存channel:
- 通道的缓存无数据,但执行读通道。
- 通道的缓存已经占满,向通道写数据,但无协程读。
Panic:
1.向已经关闭的channel写。
2.关闭已经关闭的channel。
close channel:
You needn't close every channel when you've finished with it.It's only necessary to close a channel when it is important to tell the receiving goroutines that all data have been sent.
Note that it is only necessary to close a channel if the receiver is looking for a close. Closing the channel is a control signal on the channel indicating that no more data follows.
It's OK to leave a Go channel open forever and never close it. When the channel is no longer used, it will be garbage collected.