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

SR: Browser crash on comparing a huge schema #867

Open
4 tasks done
pochea15 opened this issue Feb 25, 2025 · 1 comment
Open
4 tasks done

SR: Browser crash on comparing a huge schema #867

pochea15 opened this issue Feb 25, 2025 · 1 comment
Labels
area/sr Schema Registry scope/frontend Related to frontend changes status/confirmed A bug that is a confirmed one. Applicable only for the bug label. status/triage/completed Automatic triage completed type/bug Something isn't working

Comments

@pochea15
Copy link

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

"From a discord conversation"
We recently updated our repo to use Kafbat 1.1.0 Kafka UI over the original. One of our users has an extremely large Json schema over 12,000 lines.

They said that they were able to use the compare feature prior to us moving to the new version of Kafbat. It would just take awhile to load. Now it ends up crashing chrome. It seems to be a client side issue as there are no error logs on the backend. And nothing seems to appear in the console.

This is a schema with sensitive information removed.
https://gist.github.com/pochea15/5e2e4332fd223ee07e3e0b574ac93f31

Expected behavior

User has an understanding a schema that large is going to be slow but having it not crash is the expected behavior.

Your installation details

  1. 9a4eb69 1.1.0

Steps to reproduce

Load up https://gist.github.com/pochea15/5e2e4332fd223ee07e3e0b574ac93f31 and give it a go

Screenshots

No response

Logs

No response

Additional context

No response

@pochea15 pochea15 added status/triage Issues pending maintainers triage type/bug Something isn't working labels Feb 25, 2025
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Feb 25, 2025
Copy link

Hi pochea15! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

@Haarolean Haarolean added scope/frontend Related to frontend changes status/confirmed A bug that is a confirmed one. Applicable only for the bug label. area/sr Schema Registry and removed status/triage/manual Manual triage in progress labels Feb 25, 2025
@Haarolean Haarolean changed the title Schema Compare Will Not Load Large Schemas (Kafbat 1.1.0) SR: Browser crash on comparing a huge schema Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sr Schema Registry scope/frontend Related to frontend changes status/confirmed A bug that is a confirmed one. Applicable only for the bug label. status/triage/completed Automatic triage completed type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants