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

The call graph is throwing ISE 500 on profile visit. #39

Open
shriyanshagnihotri opened this issue Jul 17, 2016 · 3 comments
Open

The call graph is throwing ISE 500 on profile visit. #39

shriyanshagnihotri opened this issue Jul 17, 2016 · 3 comments

Comments

@shriyanshagnihotri
Copy link

shriyanshagnihotri commented Jul 17, 2016

The call graph is throwing ISE 500 on profile visit.

The UI tries to pull the png from backend but the backend returns 500.

I have installed libcgraph6 graphviz graphviz-dev OS packages. I am using debian 8.
I have installed linesman using pip.

screen shot 2016-07-18 at 12 05 55 am

screen shot 2016-07-18 at 12 06 36 am

require help!!

@shriyanshagnihotri
Copy link
Author

shriyanshagnihotri commented Jul 17, 2016

Also in one of my machine I am able to see the call hierarchy but in few machines i get "method 'disable' of '_lsprof.Profiler' objects". any idea why this is happening.

@amcfague
Copy link
Owner

amcfague commented Aug 1, 2016

You'll need to look at the server logs to see why its returning a 500--if its failing to return the PNG, chances are something is going on with your graphviz installation . Were you able to figure this out?

@shriyanshagnihotri
Copy link
Author

@amcfague : I checked the log, un-luckily after the request of graph image file from client the server takes to much time to respond and hence it times out.

Here is my request log:
"127.0.0.1 - - [2016-08-09 09:40:28] "GET /favicon.ico HTTP/1.0" 200 2406 0.327379
127.0.0.1 - - [2016-08-09 09:40:32] "GET /profiler/profiles/2f68efaa-5de7-11e6-bda9-000c29762109 HTTP/1.0" 200 7234 0.024593"

after this the server stops responding. Also what is the nominal time for computing the call graph, maybe I can adjust the timeout as per that to overcome this problem.

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

2 participants