Maximum call stack size exceeded

[rootcause]

Forum: https://www.bryntum.com/forum/viewtopic.php?f=54&t=14770

Occurred: 2 times
URL: https://www.bryntum.com/examples/calendar/basic/
Open in Rootcause

An error was logged by RootCause:

Stack trace:
Month.updateDayNumbers at https://www.bryntum.com/examples/build/calendar.module.js?443053:24491:26
Month.updateWeekStartDay at https://www.bryntum.com/examples/build/calendar.module.js?443053:24408:32
Month.set at https://www.bryntum.com/examples/build/calendar.module.js?443053:1483:44
Month.get at https://www.bryntum.com/examples/build/calendar.module.js?443053:1517:33
Month.updateDayNumbers at https://www.bryntum.com/examples/build/calendar.module.js?443053:24494:17
Month.updateNonWorkingDays at https://www.bryntum.com/examples/build/calendar.module.js?443053:24414:32
Month.set at https://www.bryntum.com/examples/build/calendar.module.js?443053:1483:44
Month.set at https://www.bryntum.com/examples/build/calendar.module.js?443053:1525:28
Month.setConfig at https://www.bryntum.com/examples/build/calendar.module.js?443053:1793:38
Month.configure at https://www.bryntum.com/examples/build/calendar.module.js?443053:1763:32

[dongryphon]

I am not able to reproduce this but did read the code implicated in the callstack. Following are my notes.

setConfig loops the config properties, and seems to hit nonWorkingDays which calls updateNonWorkingDays:

    updateNonWorkingDays() {
        this.updateDayNumbers();
    }

Inside updateDayNumbers gathers a few configs right away:

    updateDayNumbers() {
        const
            me                    = this,
            {
                weekStartDay,
                nonWorkingDays,
                hideNonWorkingDays
            }                     = me,

This triggers the initializer for weekDayStart (you see the getter calling the setter in the callstack), which ends up in updateWeekStartDay:

    updateWeekStartDay() {
        this.updateDayNumbers();
        this.calculateWeekBase();

        if (!this.isConfiguring) {
            this.updateDate(this.date, this.date);
        }
    }

While that takes us back to updateDayNumbers this should not go infinitely recursive due to the way the config initializer works. Perhaps if we had more of the callstack we could see where it starts the infinite sequence of calls.

[dongryphon]

The customer indicated that their TZ was UTC+8 but when I changed my TZ to that I was still unable to reproduce the error. Is there a way to get more entries in the callstack? The entries we've captured here are normal so we'd need 3x as many more to see the cycle most likely.