-
-
Notifications
You must be signed in to change notification settings - Fork 927
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error handling: Duplicated components after an error is thrown in a view #2645
Comments
Hi All! I believe I have an example. It is quite non-sensical, but we had something similar in real code: If you change the option in the select a few times, you'll see that new items in the list are being added and the old ones are not removed. The stack trace is not helpful, because it happens inside mithril and not in the user's code. Thank you! |
It seems to me that the issue is that |
If an exception is thrown, the update of the root.vnodes is skipped. I have created smaller flems. The more buttons you click, the more zombies you will have. Of course, this can also occur if an error is thrown in the component view(). (flems, cf. #1937). In this example, however, it appears that the number of zombies is only increased to two. This seems to be related to reentrantLock. Like flems above, if the error message is on the console, you may not need to be too afraid of the zombies. |
This is somewhat a duplicate of #2273, but I also haven't seen it mentioned in the thread or anywhere else (or maybe I missed it):
When an error is thrown in a view in Mithril, the diffing engine will often get confused and start rendering multiple copies of the same component to the page.
This seems unexpected, and I haven't seen it mentioned anywhere else. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: