-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modeling exercises
: Apollon freezes locally
#9032
Comments
I debugged for a really long time. I used Apollon as a local dependency for Artemis and could put breakpoints in the React code ( There is an infinite loop in @matthiaslehnertum, @loreanvictor do you have an idea? |
@loreanvictor sent me another insight which might be helpful:
|
I think the problem is fixable by using the signal-based change detection? This issue of causing infinite rerenders, is somehow related to the current change detection. |
@FelixTJDietrich I'm still investigating the browser freeze issue and wanted to share what I've found so far. The freeze occurs consistently when users add the following elements:
I'll keep looking into it and will update with any progress or findings. |
@egenerse Sounds like this happens specifically for container elements that can have sub elements? Maybe there is an issue in the processing or rendering here that leads to some kind of endless loop? |
This issue also occurs with a vanilla JavaScript setup. To verify, I created a separate repository, apollon-uml-vanilla-js. Given this, it appears that there’s no action required on the Artemis side. Interestingly, this issue does not appear in the React-based |
Describe the bug
In some diagrams, like BPMN and Component Diagrams, when dragging some elements on the canvas the browser freezes and then crashes.
To Reproduce
This issue only appears to exist in the development environment:
Expected behavior
No crash
Screenshots
No response
Which version of Artemis are you seeing the problem on?
7.4.2
What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: