# Memory Leak in browser?

**URL:** <https://community.fibery.io/t/memory-leak-in-browser/8512>\
**Category:** Bugs & Issues\
**Created:** [March 26, 2025, 5:28am UTC](https://community.fibery.io/t/memory-leak-in-browser/8512 "2025-03-26T05:28:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\
**Post date:** [March 26, 2025, 5:28am UTC](https://community.fibery.io/t/memory-leak-in-browser/8512/1 "2025-03-26T05:28:06Z")

</div>

Fibery tabs left open for extended periods tend to consume a lot of memory, suggesting there may be a memory leak somewhere. Related to [High memory usage (in Safari) - Bugs & Issues - Fibery Community](https://community.fibery.io/t/high-memory-usage-in-safari/249)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [April 4, 2025, 7:30am UTC](https://community.fibery.io/t/memory-leak-in-browser/8512/2 "2025-04-04T07:30:11Z")

</div>

We will check this

---

<div class="post-metadata">

**Author:** ![Sergey\_Truhtanov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sergey_truhtanov/32/13986_2.png) [@Sergey\_Truhtanov](https://community.fibery.io/u/Sergey_Truhtanov)\
**Post date:** [April 7, 2025, 9:47am UTC](https://community.fibery.io/t/memory-leak-in-browser/8512/3 "2025-04-07T09:47:30Z")

</div>

Hello.  
Sorry for the late reply.  
Could you please share your workspace URL (or what exactly you have on the screen) that is leaking? Or it appears on any tab? You may just send me in private message here in community.

Memory leaks are somewhat tricky. It can be some crazy issue in UI component or data that is hard to reproduce locally. Last time I’ve checked, leaving open tab on a workspace that we use heavily ourselves – there was no leak.

---

<div class="post-metadata">

**Author:** ![Sergey\_Truhtanov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sergey_truhtanov/32/13986_2.png) [@Sergey\_Truhtanov](https://community.fibery.io/u/Sergey_Truhtanov)\
**Post date:** [April 11, 2025, 3:42pm UTC](https://community.fibery.io/t/memory-leak-in-browser/8512/4 "2025-04-11T15:42:19Z")

</div>

Hello again.

We’ve successfully reproduced memory leak issue. It appeared our grid component is leaking. So when you open a page with a grid on it and then navigate away, some parts are left in memory. It’s not that much, but if Fibery workspace setup is changing (Fibery schema changes), previous schema is left in memory as well. Which actually can be huge, depending on your workspace configuration.

We will fix the issue with next release.

---

<div class="post-metadata">

**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\
**Post date:** [April 22, 2025, 7:37am UTC](https://community.fibery.io/t/memory-leak-in-browser/8512/5 "2025-04-22T07:37:28Z")

</div>

Awesome, much appreciated! 💕