Out of Memory Browser Error

[MathewGdows]

All,

Does anyone else get the "out of memory" error (or the "wait" indication on the browser page) on their browser when developing?  I get this very, very frequently when trying to develop in our DEV environment.  It does not matter if I'm using Edge (my normal browser) or Chrome.

This especially happens when working in the Catalog Item and/or Workflow Studio.  I am on Yokohama Patch 9, but this has been happening for a while, so I doubt it is an instance/patch issue.  I ensured my laptop has more than enough memory and no other tabs are open in Edge.

It drives me nuts since I can click on a dropdown and have to wait forever for it to allow me to pick something and then takes forever again just to load my selection.  This is only one small example.  I have to save almost every time I perform an addition in Workflow Studio or I lose everything I did between Saves/Activations.

Any suggestions on what to look at?  I asked ServiceNow and they just shrugged their shoulders at my support ticket and gave no thoughts on the issue.

Thanks

[Mark Manders]

First check with colleagues if they have the same issues. If they do, it's likely something with the instance. If they don't, it could be your machine. 

If you are able: try it on a different laptop/pc to see if that makes any difference for you.

We don't know your instance, so we don't know if anything is running that just takes up a lot of resources. Check logs, slow queries and transactions for anything that could be blocking you. 

Is it just the DEV or also other instances.

And never allow NowSupport to ignore you. They try that a lot and if you let them, they will. Especially if you aren't buying any Impact packages. The 'free' support is simply terrible, but you are entitled to it on (performance) issues. They can see more than you can, so just keep bugging them and ask for escalation if they still ignore you.

[MathewGdows]

@Mark  - I appreciate the info.  At this point, I'm noticing that it happens in Workflow Studio if my flow is 50 or more lines/actions/etc.  That is when it is a much bigger impact.  If it is maybe 25 lines/actions/etc. or smaller, it acts normal and everything is fine.  I wouldn't think it is because of how many actions the flow has, but maybe that is the reason.

I am the only one that develops, so I can't really ask anyone else to try it.  Well, I guess I could ask them to go into that flow and try and open things, but not develop directly.  It only seems to happen in our DEV environment, but that is the only location I normally develop in.  It's okay in TEST and PROD when the process/flow is running, but I don't make changes there, so I haven't exactly tested the theory/issue there.

Maybe it is just because of huge flows and I just have to "deal with it", which stinks.  I've never had this issue on any other ServiceNow system I've worked on before.  I was even wondering if processes (scheduled jobs) are running in the background at the same time and that is causing the issues.  I don't know.  I just know that it takes about 16-17 seconds between every click/dropdown/movement/etc.  It doesn't sound like much, but when you click on a dropdown, wait 17 sec, make your dropdown choice, wait 17 sec, move to save that action, wait 17 sec, then move to the next action of the flow, wait 17 sec.  It's super, super annoying and takes forever.

Maybe I'll try and take a video of the process and send that to ServiceNow to see what they think.  Again, it mainly happens in Catalog Items when working on variables and such and definitely in Workflow Studio when I have larger flows I'm creating/editing/etc.  Maybe that's normal?

Thanks again.