Apex heap size too large only for 1 user...

  • 1
  • Question
  • Updated 1 week ago
  • In Progress
Hi,

Not a new question, and through the years became quite proficient at finding cause/fixing heap issues...

But this one boggles my mind. 

Everyone can see a specific skuid page no problem.. except 1 user which had the same profile (admin) and role and access to fields... than other people that can see page properly and this 1 person gets consistently Apex heap size too large: 11736765 on the same records anyone else can see perfectly fine.

Any ideas?

I'm been trying to fix this for past 2 hours and nothing i tried worked.

Thx
Photo of Dave

Dave

  • 5,538 Points 5k badge 2x thumb

Posted 1 week ago

  • 1
Photo of Josef Lagorio

Josef Lagorio

  • 2,864 Points 2k badge 2x thumb
Are there large text-area fields in any of your models that are being queried on page load?
(Edited)
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,050 Points 10k badge 2x thumb
Joe has a good suggestion on something to check - any long text fields, or perhaps image fields that this user might happen to see larger values in? Could the page's models return more rows for this user, if the user created or owns more records than others? 

Another thing you can try is to log in as the user, then open up the browser console and enter the command skuid.model.map(). Each model will be listed, and you can click on them to drill down and see lots of properties of each. You can also see the SOQL query that each model used. Try copying that query and running it in the Salesforce developer console. You should be able to see the full results of the query (without the heap size limit, I believe) and that might help you see anything that's obviously larger for this user vs. others.
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,050 Points 10k badge 2x thumb
Also, you might compare the SOQL queries this user's page sees, against those for an unaffected user. There could be a field set up in a model's condition that's meant to filter out some records, but this user can't access that field, and the condition is therefore turned off.