Getting "Awww Snap, Out of Memory" - But What Is Causing It?

Wappler General
1

Hey folks…

I’ve been getting some “Awww Snap, Out of Memory” crashes reported within Chrome with my web app recently… any pointers as to what are the best areas to look at to minimise this?

2

@patrick or @teodor… I’ve just been looking at what I changed in the last week… and I put this line onto the body tag of the app (which is a single page app):

dmx-on:ready="browser_is_safari.value==1?m_safari.show():false"

Does this fire just once when the app loads, or could it be causing some sort of memory leak?

Also, I am assigning a variable value from the browser component as below… could this be it?

<dmx-value id="browser_is_safari" dmx-bind:value="( 
    (browser.userAgent.contains('Safari')) && (!(browser.userAgent.contains('Chrome'))) && (!(browser.userAgent.contains('iPhone')))  && (!(browser.userAgent.contains('iPad'))) 
    ||
    (browser.userAgent.contains('Safari')) && (!(browser.userAgent.contains('CriOS')))&& (browser.userAgent.contains('iPhone')) 
    )?1:0"></dmx-value>

I’ve never had this issue before, and everything else I recently added is quite standard stuff apart from this!

My fully released app where this happens is still on Wappler 3.9.7…

3

Could you please be more descriptive of your app’s tech stack… it’s pretty unclear if you’re referring to your website app or a mobile app, as well as who shows that error message

4

Thanks @Apple!

The message is coming from Chrome.

It is a web app using PHP and MySQL, running on AWS servers.

Is there other info that may be useful?

5

That’s enough, thanks!

This sounds a Patrick-Teodor problem, you’ll probably have to wait for them to troubleshoot this kind of problem. They’ll probably ask you for a link so they can access your website and see the problem

1 Like
6

One of my users has just reported it being an issue in Chrome, but not in Firefox… :man_shrugging:

7

Looks like it is a Chrome specific thing…