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

Uncaught RangeError: Maximum call stack size exceeded #52

Closed
jrmgx opened this issue Jul 2, 2014 · 11 comments
Closed

Uncaught RangeError: Maximum call stack size exceeded #52

jrmgx opened this issue Jul 2, 2014 · 11 comments

Comments

@jrmgx
Copy link

jrmgx commented Jul 2, 2014

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

@erikdubbelboer
Copy link
Owner

Did it give you any stack trace?

@jrmgx
Copy link
Author

jrmgx commented Jul 3, 2014

No it did not

@doodirock
Copy link

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.

@doodirock
Copy link

Looks like there is a recursive function somewhere that is being called over and over

@flenczewski
Copy link

which browser?

@doodirock
Copy link

Chrome on Mac. I'll test on others now.

@doodirock
Copy link

Firefox "works" but chokes when going past 200k

@erikdubbelboer
Copy link
Owner

What do you have count_elements_page set to? I suggest setting it to 1000.

I just tested it in Chrome on Mac and everything works fine. Even if I don't set count_elements_page.
My test is here: http://dubbelboer.com/phpRedisAdmin/?view&s=1&key=52test

The only javascript being executed is js/frame.js which doesn't contain any recursion.
Could it maybe be some Chrome plugin you have that uses jQuery and interacts with the page?

@doodirock
Copy link

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.

@erikdubbelboer
Copy link
Owner

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.

@doodirock
Copy link

Thanks. Feel free to close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants