Hello,
Once I set live an APP i am developing for internal use its giving me Error: Out of Memory. I noted that This is a common problem with bubblers thus I am writting to see if anybody found any work around. On top of this I also filled a Bug Report.
Thanks in Advance
Hello
This is most probably not due to bubble.
I’m positive this is caused by your device due to low or insufficient RAM.
But this is happening on every PC, even on my Gamming Set up.
Would it be possible that your app is performing heavy processes which would use up the device’s RAM? Even if that’s the case, I think Bubble wouldn’t throw an error like that. At least I haven’t experienced that error when building highly complex apps.
I call around 1-2 mb of API data when you log in, but I’ve called 10mb + on the past and no such errors came up. While looking for similar problems I noted that this was a comon error on bubbles end a few months Ago and I am really hoping that this is my problem 
.
Anyways, I wrote to support and will share info with you once we settle this with the support.
Really thanks for trying to help me, I appreciate it a lot.
This almost only happens to me in the editor after I surpass around 4gb of browser memory usage
Does this happen in version-test?
I’ve seen this in a live app once. I had created a plugin that was pulling in data from google calendar and throwing the events into a custom plugin state using a pseudo data type. It could handle 0-200 items in the state ok. 200-400 would start being slow/sluggish. Over 200 would usually cause issues. But, the issues only happened after updating and publishing the state several times. It was super weird. The issue being that the browser would simply crash.
I’d start by watching network traffic and seeing what comes in.
Yeah same, I get an error when I roughly reach somewhere around that too. But correct me if I’m wrong @ilirkras, this error shows up not on the editor, but on your app, correct?
If its the editor, then that would make sense.
This error shows on app it self, when in debug mode it comes up even faster, when in live mode it is slightly better but at some point it comes up. And this happens in just one section in my app/ when interacting with one table (I call it clients).
How much data are you throwing into the RG? What’s the data structure like?
I know we have had crashes in our product in the past before we were using pagination and used only infinite scroll.
I have around 1k records called client and yeah I am using pagination. Another thing I am doubting is I use a filter to select only clients that are assigned at some user ID and for this I look if an ID exist in a API table. But this is happening even when this filter is blank (so this constraint is ignored).
It uses only pagination and I am thinking to set to infinit scroll and see how it performs.
You load 1000 items, then paginate thru them? 
Or, you call 1 page of data at a time? Filtering client side slows stuff down. Advanced filters are ridiculously inefficient a lot of the time. Super useful but not super efficient.
I’ve had an app crash and show this error in addition to the the Bubble error stating “Sorry we ran into a temporary bug and…” which I think was related. On that app the crash was triggered by a plugin used to upload files to AWS.
Are you able to replicate this error with any consistency? Do you know which actions are increasing the memory load on the browser? Have you taken a look at the memory tab in dev tools?
This topic was automatically closed after 70 days. New replies are no longer allowed.
