[REACT] SCHEDULER - When updating events, console error with "Maximum call stack size exceeded"

[eduardo cotta]

Hello,

We are facing some issue when we load more than 500 events on the Bryntum Scheduler, and it's returning the following stack trace on console:

AssignmentStoreMixin.js:13 Uncaught RangeError: Maximum call stack size exceeded
    at get storage [as storage] (AssignmentStoreMixin.js:13:68)
    at AssignmentStore.getEventsAssignments (CoreAssignmentStoreMixin.js:40:13)
    at get assigned [as assigned] (CoreHasAssignmentsMixin.js:22:62)
    at get assignments [as assignments] (EventModelMixin.js:507:1)
    at ClassDefEx.applyResourceId (EventModelMixin.js:454:21)
    at set resourceId [as resourceId] (EventModelMixin.js:449:60)
    at set resource [as resource] (EventModelMixin.js:443:20)
    at AssignmentStore.assignEventToResource (AssignmentStoreMixin.js:355:27)
    at ClassDefEx.applyResourceId (EventModelMixin.js:477:22)
    at set resourceId [as resourceId] (EventModelMixin.js:449:60)

We are loading these events as we scroll down the screen so we don't load the 500 altogether, it's 100 events in each call.

We do our update on the Scheduler events by creating a React useState with a type that we created that has the properties of an event. When we want to update the events, we fetch for new events, and after the response, we update the useState with all events including the new ones, and maybe this is causing some problem. And we pass this useState variable to Scheduler events property.

We saw that in the forum we have another with a similar error (viewtopic.php?f=51&t=16041&p=79916#p79916), that's not fixed yet, but we wanted to make sure that we understood right, because it's a big problem on our system.

We also tried to solve by updating to 5.1.2 version, and it didn’t work.

[marcio]

Hello eduardo cotta,

Thanks for reporting, I added a note to the ticket about this issue, please watch the issue to be notified as soon as it get fixed.

[eduardo cotta]

Thanks Marcio!

Just to confirm, do you have any estimated time for this issue to be fixed?

[marcio]

Hey eduardo,

Unfortunately, we can't assure a date to fix it, but as you'll see in the ticket https://github.com/bryntum/support/issues/1996#issuecomment-1235169836, as soon as that ticket got marked as resolved, it'll be available in the nightly build in the day after.