Question Site is randomly crashing for me

[Dionicio3]

Hello! Sometimes while I browsing gbatemp, google chrome just randomly brings up the "Aw snap, something went wrong" page. It happens to be on computer and on mobile, it is dry annoying, and I'm wondering if anyone else has this problem. Thanks

 

[Dionicio3]

Ok, I have some more info, it seems to crash more when there is a popup (edit screen, user screen, viewing warnings)

 

[how_do_i_do_that]

If your using the standard 32bit version, your likely running out of memory. This can happen when you got a lot of tabs open. 32bit version of Chrome can only address upto 2GB of RAM, this is a limitation of anything 32bit not just Chrome. It is not something you can fix, you can download and use the 64bit version of Chrome to delay this problem.

 

[Dionicio3]

If your using the standard 32bit version, your likely running out of memory. This can happen when you got a lot of tabs open. 32bit version of Chrome can only address upto 2GB of RAM, this is a limitation of anything 32bit not just Chrome. It is not something you can fix, you can download and use the 64bit version of Chrome to delay this problem.

If I was running out of memory, I would be able to tell, so it's not that

 

[Subtle Demise]

When viewing on mobile Chrome, the site won't crash, but it will lock up periodically when scrolling threads and even more so when writing a reply in the quick reply box. The keyboard becomes very unresponsive.

 

[how_do_i_do_that]

I got a system with 128GB of RAM and pages crash all the time on the 32bit version of Chrome. If your referring to system messages of running out of RAM, Chrome, Windows, and Android all memory paging so you don't physically run out of memory space.

Spoiler

When the flash plugin crashes, the cause has always been it ran out of allotted memory. The majority of pages that crash is due to running out of allotted memory. Scripts that require more memory over time can cause a page to crash.

The whole point is the 32bit version of Chrome sucks at memory management at longer periods of time when you run it.

---

When viewing on mobile Chrome, the site won't crash, but it will lock up periodically when scrolling threads and even more so when writing a reply in the quick reply box. The keyboard becomes very unresponsive.

Not being able to access the on screen keyboard IS an example of Android running out of memory.

 

[Subtle Demise]

I got a system with 128GB of RAM and pages crash all the time on the 32bit version of Chrome. If your referring to system messages of running out of RAM, Chrome, Windows, and Android all memory paging so you don't physically run out of memory space.

Spoiler

View attachment 86527

When the flash plugin crashes, the cause has always been it ran out of allotted memory. The majority of pages that crash is due to running out of allotted memory. Scripts that require more memory over time can cause a page to crash.

The whole point is the 32bit version of Chrome sucks at memory management at longer periods of time when you run it.

---


Not being able to access the on screen keyboard IS an example of Android running out of memory.

So it's a general performance issue then.

 

[how_do_i_do_that]

So it's a general performance issue then.

More or less. That is why when Android came out it had anywhere from 256-512MB of RAM and has only increased in RAM to the 2GB limit today. (4GB of RAM or more use a 64bit version of Android)

Back then the unresponsive keyboard issue was more prevailent. You don't see alot of this issue on today's android phones.