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

Large options in calcite-select crashed the browser with a "DevTools was diconnected..." and snap! #5919

Closed
caronrob2000 opened this issue Dec 6, 2022 · 5 comments
Labels
0 - new New issues that need assignment. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. incomplete issue report New issues missing important information, and unless provided, they will be closed after 5 days. need more info Issues that are missing information and/or a clear, actionable description. needs triage Planning workflow - pending design/dev review.

Comments

@caronrob2000
Copy link

Actual Behavior

Hi,

I have 2 calcite-select having 4000 options each (business required this way). Creating the DOM is fast but when it gets to the calcite core function to make its thing, it takes a long time. The CPU goes way up, memory goes high and suddenly "snap" the browser.

The function "populateInternalSelect" that caused it.

Thanks

Expected Behavior

Should populate the select fast since this is a regular select-option

Reproduction Sample

Just have 2 large calcite-select

Reproduction Steps

The code is too large so like I said before, just have 2 large calcite-select options and see.

Reproduction Version

bete.97

Relevant Info

No response

Regression?

No response

Impact

No response

Esri team

N/A

@caronrob2000 caronrob2000 added 0 - new New issues that need assignment. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. needs triage Planning workflow - pending design/dev review. labels Dec 6, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 6, 2022

It looks like this issue is missing some information:

  • A codepen, codesandbox, or jsbin that reproduces the issue. Alternatively, a documentation sample can be used if the issue is reproducible. If you are experiencing build or Node related errors, please provide a GitHub repo for the sample.

Issues without reproduction samples may not be prioritized. If you were unable to create a sample, please try to answer any questions that arise once development begins. Thanks for your understanding.

@github-actions github-actions bot added the incomplete issue report New issues missing important information, and unless provided, they will be closed after 5 days. label Dec 6, 2022
@macandcheese
Copy link
Contributor

Related: #1460

@geospatialem
Copy link
Member

@caronrob2000 Is there a snippet or code sample you could provide for additional context?

We'd like to explore a workaround to mitigate prior to a fix.

@geospatialem geospatialem added the need more info Issues that are missing information and/or a clear, actionable description. label Mar 21, 2023
@geospatialem
Copy link
Member

@caronrob2000 Is there a snippet or code sample you could provide for additional context?

We'd like to explore a workaround to mitigate prior to a fix.

@caronrob2000 Re-pining if there's a snippet or code sample we could add for additional context to troubleshoot. Without the additional context, we will be closing the issue next month.

@geospatialem
Copy link
Member

Closing out the issue per #5919 (comment). You can re-open this issue with additional context for Calcite team members to explore a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. incomplete issue report New issues missing important information, and unless provided, they will be closed after 5 days. need more info Issues that are missing information and/or a clear, actionable description. needs triage Planning workflow - pending design/dev review.
Projects
None yet
Development

No branches or pull requests

4 participants