Skip to content
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

[Bug Report] Placing tabs inside a modal dialog causes CPU usage to spike to 100% when closing the dialog with destroy-on-close enabled #20228

Open
stgogm opened this issue Sep 24, 2020 · 5 comments
Labels

Comments

@stgogm
Copy link

stgogm commented Sep 24, 2020

Element UI version

2.13.2

OS/Browsers version

Ubuntu 20.04, Chromium 85.0.4183.121/Firefox 80.0.1

Vue version

2.6.12

Reproduction Link

https://jsfiddle.net/swzvnj9a/2/

Steps to reproduce

Create a el-dialog with destroy on close enabled.
Place an el-tabs tabs inside.
Close the dialog.
CPU usage is 100% ...

What is Expected?

The dialog closes without hanging the browser.

What is actually happening?

The dialog hangs the browser on close.

@mattjin
Copy link

mattjin commented Nov 23, 2020

+1

2 similar comments
@DreFalPoetry
Copy link

+1

@wdschn
Copy link

wdschn commented Jan 13, 2021

+1

@enguerrand-dilitrust
Copy link

Will be fixed by #17380

@stale
Copy link

stale bot commented Apr 28, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants