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

Bad performance #94

Closed
Majstr opened this issue Jan 22, 2015 · 6 comments
Closed

Bad performance #94

Majstr opened this issue Jan 22, 2015 · 6 comments

Comments

@Majstr
Copy link

Majstr commented Jan 22, 2015

I have low memory on my virtual machine and it takes forever to load error page. Some times I even get out of memory error. I am guessing is problem in stack trace. Can I limit stack trace?

@JanTvrdik
Copy link
Contributor

Did you change any of the default limits? (maxDepth, maxLen)?

@Majstr
Copy link
Author

Majstr commented Jan 22, 2015

No nothing. I tought this parameters were only for var dump. How can I change that?

@JanTvrdik
Copy link
Contributor

Just to clarify – by „error page“ you mean the bluescreen, right?

You can try reducing maxDepth:

Tracy\Debugger::$maxDepth = 1;

Or you can try to use Tracy 2.3-dev which uses more efficient way to dump variables.

@Majstr
Copy link
Author

Majstr commented Jan 22, 2015

Yes bluescreen. I will try to reduce it.

@Majstr
Copy link
Author

Majstr commented Jan 22, 2015

I tried lower maxDepth but it has no effect. Problem is in 'call stack' and 'coused by'. I also try to lover maxLen to 10 but in 'call stack' and 'coused by' still show 30+ rows.

@JanTvrdik
Copy link
Contributor

My bad, Tracy\Debugger::$maxDepth does not actually affect bluescreen performance because bluescreen uses directly Tracy\Dumper.

In that case please try 2.3-dev.

@dg dg closed this as completed Jan 31, 2015
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

3 participants