Timeline for Maximum stack depth reached: 12
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2018 at 21:56 | history | tweeted | twitter.com/StackSalesforce/status/1018252880694992896 | ||
| Jul 11, 2018 at 13:28 | answer | added | Jaap Scheper | timeline score: 0 | |
| Dec 15, 2015 at 10:21 | comment | added | Willem Mulder | Thanks! We had the idea it might be due to some serialization issue where there is two objects that have lookups to each other and then when either of the objects is compared to something, or used in a hashmap (set), then it will be serialized and the serializer gets in a loop somehow... But we can't know for sure. | |
| Dec 14, 2015 at 17:50 | comment | added | metadaddy | No response yet... Rattling some cages... | |
| Dec 10, 2015 at 13:46 | comment | added | Willem Mulder | @metadaddy any news on this? We are still having this issue and we really hope this can be fixed at some point... | |
| Nov 10, 2015 at 9:20 | comment | added | Willem Mulder | Hi @metadaddy that would be great. It's issue 12462303. Thanks! | |
| Nov 10, 2015 at 5:13 | comment | added | metadaddy | I'm asking in the internal Apex Chatter group. Do you have a case number? | |
| Nov 5, 2015 at 13:26 | comment | added | Willem Mulder | @sfdcfox thanks so much! Really looking forward to his answer. | |
| Nov 4, 2015 at 23:17 | comment | added | sfdcfox♦ | I just asked Pat Patterson if he might be able to shed some light on this. He's an internal salesforce.com guy that's pretty awesome, so he might be able to help. | |
| Nov 4, 2015 at 22:11 | comment | added | Willem Mulder | @sfdcfox it's only happening when debugging is on (via debug flag or if developer console is open) and that's really annoying because that means that running code or tests via the developer console is impossible because we always get the Stack Depth error. SF support has given up I think, so we're still in the dark. | |
| Nov 4, 2015 at 18:32 | answer | added | user6856 | timeline score: 1 | |
| Sep 30, 2015 at 20:08 | comment | added | Willem Mulder | Hey @sfdcfox thanks so much for the effort! Salesforce support is stuck on it for 14 days as well, and they assumed that it had to do with some null assignment, which sounds unlikely. Even more because we've just found that it only occurs for one specific user (an Admin) and not for the other users (also Admins). This makes the issue even less predictable. I'll leave the question open for others that might have possibly had the same issue... | |
| Sep 30, 2015 at 16:16 | comment | added | sfdcfox♦ | FWIW, I can't duplicate "stack depth exceeded: 12"; I know about other limits, like 17 and 1001, but I wrote several different trivial types of code to try and find what limit you've run into, and I can't seem to find anything at all. You might need a closer look at your code. | |
| Sep 30, 2015 at 16:04 | comment | added | sfdcfox♦ | There are multiple "stacks" in the system, such as the trigger context stack, the function call stack, the regular expression stack (I just found this one by googling, actually), and probably others. My guess is that there's some maximum number of references you can traverse in one object's memory graph, and you managed to break it. | |
| Sep 30, 2015 at 14:04 | history | asked | Willem Mulder | CC BY-SA 3.0 |