# Kubo v0.21.0-rc1 is out!

**URL:** <https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557>\
**Category:** News\
**Tags:** go-ipfs, kubo\
**Created:** [June 12, 2023, 4:22pm UTC](https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557 "2023-06-12T16:22:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hacdias](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hacdias/32/8255_2.png) [@hacdias](https://discuss.ipfs.tech/u/hacdias)\
**Post date:** [June 12, 2023, 4:22pm UTC](https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557/1 "2023-06-12T16:22:52Z")

</div>

## Kubo v0.21.0-rc1 is out!

See:

- Code: [Release v0.21.0-rc1 · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/releases/tag/v0.21.0-rc1)
- Binaries: [/ipns/dist.ipfs.tech/kubo/v0.21.0-rc1/](https://dist.ipfs.tech/kubo/v0.21.0-rc1/)
- Docker: `docker pull ipfs/kubo:v0.21.0-rc1`
- Release Notes: [kubo/docs/changelogs/v0.21.md at release-v0.21.0 · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/blob/release-v0.21.0/docs/changelogs/v0.21.md)

---

<div class="post-metadata">

**Author:** ![hacdias](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hacdias/32/8255_2.png) [@hacdias](https://discuss.ipfs.tech/u/hacdias)\
**Post date:** [June 12, 2023, 4:23pm UTC](https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557/2 "2023-06-12T16:23:15Z")

</div>



---

<div class="post-metadata">

**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\
**Post date:** [June 14, 2023, 12:50am UTC](https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557/3 "2023-06-14T00:50:37Z")

</div>

Note, we have found a pretty bad goroutine leak that makes the service performance bad and increasingly (but very slowly) increase memory usage.

> <https://github.com/libp2p/go-libp2p-kad-dht/issues/849>
>
> @Jorropo reports:
> Hey we have a goroutine leak somewhere in libp2p, is most lik…ely a deadlock does not happear with kubo v0.20 (libp2p v0.27.3) but do with kubo v0.21-rc1 (libp2p v0.27.5), I was trying to bisect it but it sometime does not appear so it made my bisect wrong.
> Tested with v0.28.0 and v0.27.6 both still have the issue.
> Here is the profile and screenshot https://ipfs.io/ipfs/QmZpLiWizT6HmnbSjWrwzcp7oAdSYo9e9fsZGQh3Zdd7wM
> Getting stuck here:
> https://github.com/libp2p/go-libp2p/blob/b4c9fed04afd7874c7390162481b67caa783d169/p2p/protocol/identify/id.go#L406
> https://github.com/libp2p/go-libp2p/blob/b4c9fed04afd7874c7390162481b67caa783d169/p2p/host/eventbus/basic.go#LL40C8-L40C8
> https://github.com/libp2p/go-libp2p/blob/b4c9fed04afd7874c7390162481b67caa783d169/p2p/host/eventbus/basic.go#L397
> You can start a new v0.21.0-rc1 Kubo node with accelerated DHT client (to generate a bunch of connection, you can also use the default client but will grow more slowly) and do ipfs diag profile then checkout goroutine.pprof most often has the issue.
> 
> 
> \---
> 
> Issue being discussed here https://filecoinproject.slack.com/archives/C03FFEVK30F/p1686692108230159

We will fix this soon.

---

<div class="post-metadata">

**Author:** ![hacdias](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hacdias/32/8255_2.png) [@hacdias](https://discuss.ipfs.tech/u/hacdias)\
**Post date:** [June 15, 2023, 1:28pm UTC](https://discuss.ipfs.tech/t/kubo-v0-21-0-rc1-is-out/16557/4 "2023-06-15T13:28:33Z")

</div>


