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
Uncaught RangeError: Maximum call stack size exceeded #52
Comments
Did it give you any stack trace? |
No it did not |
same issue. Anytime I list out a huge group of ids EX: listing:244, listing:245 above 70k I get a failure to load anything. |
Looks like there is a recursive function somewhere that is being called over and over |
which browser? |
Chrome on Mac. I'll test on others now. |
Firefox "works" but chokes when going past 200k |
What do you have I just tested it in Chrome on Mac and everything works fine. Even if I don't set The only javascript being executed is js/frame.js which doesn't contain any recursion. |
That test looks fine with 164 keys (and so does my own install), but I'm talking about 149,990 keys at a time. The side bar has to load all of them at once and it basically fails. |
Ok, the original posted mentioned "60k keys in a subset", not normal keys. phpRedisAdmin is not really designed to handle that many normal keys. It uses the KEYS command which is not really suitable for production environments (see warning on the redis page). At some point PHP will also run out of memory with too many keys (see some other closed issues). Until I have the time rewrite the whole key handling using SCAN I suggest using a solution like https://redsmin.com/ when handling with that many keys. |
Thanks. Feel free to close this out. |
I have a javascript error :
Uncaught RangeError: Maximum call stack size exceeded
when I load a server with more than 60k keys in a subset
I think the javascript engine goes mad, the error pops out of jquery.js file
The text was updated successfully, but these errors were encountered: