[SalesForce] “Maximum stack depth reached: 3” when doing String.replaceAll()

I am getting a strange "Maximum stack depth reached: 3" when doing a String.replaceAll() with bigger Regex on a quite big string (40 lines of text).
I am trying to remove any comments and literal strings out of Apex Class source code.

...
private static final Pattern COMMENTS_LITERALS_PATTERN = Pattern.compile('(/\\*([^*]|[\\r\\n]|(\\*+([^*/]|[\\r\\n])))*\\*+/)|(//.*)|\'.*\'');

String sourceCode = 'long text around 40';
String cleanedBody;

Matcher commentsLiteralsMatch = COMMENTS_LITERALS_PATTERN.matcher(original.Body);
if(commentsLiteralsMatch.find()) {
     cleanedBody = commentsLiteralsMatch.replaceAll('');     
}
...

But the small number 3 really looks to low for me to be any limit.

Do you have an explanation for this or did you experience similar behaviors?!

Best Answer

My guess is that you're reaching a limit on nested groups in your regular expression.

You could try splitting it into two separate match patterns:

'/\\*([^*]|[\\r\\n]|(\\*+([^*/]|[\\r\\n])))*\\*+/'
'(//.*)|\'.*\''

And making two passes on sourceCode.

As for matching C-style comments, check out this Stack Overflow question.

Related Solutions

[SalesForce] Maximum stack depth reached: 1001

I am confused as to what you are really trying to accomplish with this structure. You don't need to create any logic for the actual order of execution (which, correct me if I am wrong, it appears you are trying to do here). Triggers have a very specific order of execution. It will actually run through your trigger several times to hit before and after logic.

Wouldn't it be much easier to do something like:

trigger OpportunityTrigger on Opportunity (after insert, after update, before delete) {
    if(Trigger.isAfter && Trigger.isInsert){
        OpportunityHandler.createScheduleLines(Trigger.newMap);
    }

    if(Trigger.isAfter && Trigger.isUpdate){
        OpportunityHandler.adjustScheduleLines(Trigger.newMap, Trigger.oldMap);
    }

    if(Trigger.isBefore && Trigger.isDelete){
        OpportunityHandler.removeScheduleLines(Trigger.oldMap);
    }

}

public class OpportunityHandler{

    public static void createScheduleLines(Map<Id, Opportunity> newMap) {
        // logic
    }

    public static void adjustScheduleLines(Map<Id, Opportunity> newMap, Map<Id, Opportunity> oldMap) {
        // logic
    }

    public static void removeScheduleLines(Map<Id, Opportunity> oldMap) {
        // logic
    }

}

Let Salesforce worry about the order they are executed.

[SalesForce] Maximum stack depth reached: 12

Periodically this type occurs for us on the cs11 sandbox. Today is one such example. In the past I found if I refactor code, it will change which line the occurs and what depth it is reporting the error, but there is simply no way to resolve it. I think in our case it is related to some sort of bug when you call static methods to prepare values for a constructors super() call. It is only one set of classes where the error occurs. So far it has only been running test methods. If I report it to salesforce, by the time they get around into looking into it, the problem is gone. I have not seen this error on any other sandbox, even ones with the exact same code...

Best Answer

Related Solutions

[SalesForce] Maximum stack depth reached: 1001

[SalesForce] Maximum stack depth reached: 12

Related Topic