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

[Tags] Search: Uncaught RangeError: Maximum call stack size exceeded #4797

Open
GitHubUserDev12345 opened this issue Aug 1, 2019 · 1 comment

Comments

@GitHubUserDev12345
Copy link

commented Aug 1, 2019

When filtering of 490 tags in PimCore Backend (found in version 5.7.3 and still there in version 6.0.5) you get an Javascript "Uncaught RangeError".

How to reproduce

  • Open PimCore Backend
  • Settings ->Tag Configuration
  • Add 490 different tags
  • Search for your word
  • Look at the JS Error in the Developer Console in your browser ()

Uncaught RangeError: Maximum call stack size exceeded
at RegExp.exec ()
at RegExp.[Symbol.replace] ()
at String.replace ()
at Object.encodeString (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
at Object.doEncode [as encodeValue] (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
at encodeObject (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
at Object.doEncode [as encodeValue] (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
at encodeObject (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
at Object.doEncode [as encodeValue] (ext-all.js?_dc=d2acc6e0bbf363175975fce77af0557b017739cb:22)
Show 170 more frames

@brusch brusch changed the title pimcore/pimcore PimCore Tag Search: Uncaught RangeError: Maximum call stack size exceeded [Tags] Uncaught RangeError: Maximum call stack size exceeded Aug 1, 2019

@brusch brusch changed the title [Tags] Uncaught RangeError: Maximum call stack size exceeded [Tags] Search: Uncaught RangeError: Maximum call stack size exceeded Aug 1, 2019

@jones1008

This comment has been minimized.

Copy link

commented Aug 13, 2019

this seems to be the same issue as #4725.
This is probably only tested with Chrome which gives a different error message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.