Error "Aw, Snap! - Low Memory" Solution

Jeff Trzaska

Recently we ran into an issue trying to edit a 9,000+ line journal entry. We would navigate to the journal entry. We could view the journal entry, but when trying to edit it, the browser screen would go a little grey like it is “not responding”, then eventually a mostly blank screen would replace the journal entry screen with a Google Chrome error “Aw, Snap!” and the error was low memory. Through trial and error, we found these combination of steps would resolve the issue (just barely).

• Completely shutdown and restart your computer
• Do not open any other application than Google Chrome. Only open Chrome in Incognito Mode.
• Login into FE and navigate to the journal entry.
• Press F12 on your keyboard . This will open up a panel on the right of the screen (it is the developer tools, but that isn't relevant to this issue).
• On the left side of the screen, right click on the refresh button and choose “Empty Cache and Hard Reload”. You can close the panel that you opened with F12.
• Light a candle
• Attempt to edit the journal entry.
  • This may look like your past, failed attempts but you just have to wait.

At this point the JE was able to be edited. When we tried to Validate and Save, we got the same error as before. When we reopened FE, we found that the JE had been saved and was able to be posted.

Hope this helps.

Kevin Brazell

@Jeff Trzaska
I've seen that error before but in the bank rec window in webview when it's a large bank rec. It may be beneficial to bring that up to FE Support so they can document and look into it. Also do you know if you get the same errors / issues in a browser other than chrome?

Jeff Trzaska

@Kevin Brazell

It was brought up to FE/BB Support. They were their usual, helpful selves.

We do not use other browsers for IT/Firewall/Logistics reasons. I don't know what those are exactly, but our IT people do. The fact is, there is no reason this should not run well in Chrome as that is the most popular browser.

Paul Wu

@Jeff Trzaska:

@Kevin Brazell

It was brought up to FE/BB Support. They were their usual, helpful selves. -

We do not use other browsers for IT/Firewall/Logistics reasons. I don't know what those are exactly, but our IT people do. The fact is, there is no reason this should not run well in Chrome as that is the most popular browser.

So support was basically unable to provide any support whatsoever and you have to get your internal IT dept to help or use your own knowledge and technical skills to solve.
Have booked marked this, but luckily we don't have such massive JE's. Or now I am aware to limit the row numbers.

Roberta A. Gilbert

@Jeff Trzaska
How much RAM does your computer have? Browser tabs can use quite a bit of memory, and I would say the minimum required to run NXT efficiently, along with email (Google, in our case) and Excel, is 16 GB. I use at least 4 modules of NXT daily (FE, RE, Merchant Services, and Tuition Mgmt) so preferably 32 GB of RAM to be able to operate in all programs simultaneously without buffering or waiting for the software to catch up. (I'm running Windows 11, and most of my colleagues are on a Mac.)

Jeff Trzaska

@Roberta A Gilbert

Hello Roberta, my coworker who had the issue contacted our IT department first and they did add RAM. I don't know how much it started with, or how much was added. Regardless, they were still getting the error. So the thinking is, even though it said, “low memory”, it probably wasn't the issue, or the entire issue.

The more annoying part is that this was never an issue with DB view. I'm not against change. I prefer things to be continually improved, but “improved” is the key word. Also it would be nice if the people making the “improvements” understood what was happening and what they broke with their improvements.