I cannot see the profiles listed in the dropdown of webgrind

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I set a profile_log as the output directory for xdebug which is in root 
folder.
2. I set the same location in webgrind config file also
3. I have necessary permissions to read and write into that file
4. Still I dont see any profiles listed in the webgrind dropdown

What is the expected output? What do you see instead?
It should actually show all the profiles in the dropdown. I run one 
website other than webgrind. Profile was getting created in the output 
folder I mentioned for xdebug. But it was not showing up in the profile 
dropdown in webgrind

What version of the product are you using? On what operating system?
Webgrind I am using the latest version and my operating system is windows 
XP. 

Original issue reported on code.google.com by rethees...@gmail.com on 22 May 2009 at 11:42

[GoogleCodeExporter]

If you have verified that you can see actual cachegrind files being generated 
in your profiler_output_dir location, then it sounds like webgrind just doesn't 
see them.

I found today that having the %s script name piece in the profiler_output_name 
file format mask would result in webgrind not seeing any of the cachegrind 
files that I verified were in my profiler_output_dir.

You might try commenting out the profiler_output_name, thereby letting it 
default to cachegrind.out.%p , generate some cachegrind files that are in that 
format, and see if webgrind can see those.

Original comment by demon.g...@gmail.com on 3 Sep 2010 at 8:54

[GoogleCodeExporter]

I had the same problem and clicked on "Update" and everything went fine.

Maybe there could a link saying "Refresh" or something like that that would 
make things more user friendly.

The way things were displayed, I thought it was automatically refreshed when 
page was reloaded.  It seems it's not the case...

Original comment by maximejo...@gmail.com on 31 May 2011 at 2:39

[GoogleCodeExporter]

Hello,

I cannot see the file list on the Webgrind interface

I installed the Xdebug - Debugger and Profiler Tool for PHP and the Webgrind - 
Xdebug Profiling Web Frontend in PHP.

I'm using PHP Version 5.3.3, and the phpinfo() acknowleges:

* Zend Scripting Language Engine: Zend Engine v2.3.0, Copyright (c) 1998-2010 
Zend Technologies with Xdebug v2.1.1, Copyright (c) 2002-2011, by Derick Rethans
* json support enabled
* json version 1.2.1

I added the following configuration on the php.ini, which works fine and 
generates the files as expected.

--
zend_extension = C:\Program Files\PHP\ext\php_xdebug-2.1.1-5.3-vc9.dll 
xdebug.profiler_output_dir = 
C:\Users\HOME\Documents\Rui\webserver\localhost\webgrind\logs 
xdebug.profiler_output_name = cachegrind.out.%u xdebug.profiler_enable = 1
--

I configured the Webgrind properly but the frontpage does not show the file 
list.
I can confirm that in the access_log the 
http://localhost/webgrind/index.php?op=file_list file is queried. If I acess 
the file directly it shows the following output:

--
[{"filename":"cachegrind.out.1308739059_896251","invokeUrl":"C:\\Users\\HOME\\Do
cuments\\Rui\\webserver\\localhost\\index.php\r","filesize":"808B"},{"filename":
"cachegrind.out.1308739053_518141","invokeUrl":"C:\\Users\\HOME\\Documents\\Rui\
\webserver\\localhost\\index.php\r","filesize":"808B"},{"filename":"cachegrind.o
ut.1308739047_778117","invokeUrl":"C:\\Users\\HOME\\Documents\\Rui\\webserver\\l
ocalhost\\index.php\r","filesize":"808B"},{"filename":"cachegrind.out.1308739042
_115154","invokeUrl":"C:\\Users\\HOME\\Documents\\Rui\\webserver\\localhost\\ind
ex.php\r","filesize":"808B"}]
--

I used the following browsers, running on Windows Vista, none with success:

    FireFox 4.0.1
    Internet Explorer 7.0.60001.18000
    Google Chrome 12.0.742.100

Nevertheless I cannot see the file list on the Webgrind interface. 

You can see the formated version of this post at: 
http://www.void7.com/articles/webgrind_filelist_not_shown.php (easy to read).

Rui

Original comment by rui.pcoe...@netcabo.pt on 22 Jun 2011 at 11:05

[GoogleCodeExporter]

Any progress with this? I have the same problem on Ubuntu 11.10. Xdebug seems 
installed ok and webgrind doesnt show any cachegrind.out file

Original comment by shaka...@gmail.com on 17 Jan 2012 at 11:39

[GoogleCodeExporter]

Do you get eny php errors in the apache / php error log?

Do you get any Javascript errors in the browser console?

(The project has moved to github. Make sure you have the latest version)

https://github.com/jokkedk/webgrind

Original comment by oett...@gmail.com on 17 Jan 2012 at 11:56

[GoogleCodeExporter]

Hi, I download the lastest and unique zipped file github (oldest jan 2011). I 
find the real cause of my problem.

Ubuntu 11.10 provides 2 differents php.ini files:
/etc/php5/cli/php.ini

And /etc/php5/apache2/php.ini.

I set all the config on the first, that was wrong. The currently used is 
/etc/php5/apache2/php.ini.

It was easy to chech the php.ini loaded from phpinfo() function. Sorry for the 
noise. Great app.

Original comment by shaka...@gmail.com on 17 Jan 2012 at 9:28

[GoogleCodeExporter]

Super!

Original comment by adwor...@oettinger.dk on 19 Jan 2012 at 11:32

[GoogleCodeExporter]

Had the same problem, files where listed in the select box but after selection 
no data on the screen.

Problem was that in config.php

static $storageDir = '/storage';
static $profilerDir = '/profiler';

point to the root where the should point to the subdir of the webgrind running 
directory:

static $storageDir = './storage';
static $profilerDir = './profiler';

Changing that solved the matter.

Original comment by h.verou...@free.fr on 14 Apr 2012 at 12:01

[GoogleCodeExporter]

I had a custom path for Xdebug output files. These files did not appear to have 
permissions. Providing permissions(0777) to the files worked for me. I am using 
Linux Fc15, 64bit.

Original comment by echo102d...@gmail.com on 17 Jul 2012 at 3:03

[GoogleCodeExporter]

Had the same problem on Win 7. Think I fixed it(or rather, understand). xDebug 
keeps on rewriting the profile output file, so it keeps active locks on it. 
Webgrind is built to skip the file that xdebug is currently outputting. if it 
reads this file, it will  So it will always miss your current profile until the 
locks are released. Blame it mostly on the bad design of both pieces of s/w.

Original comment by helixl...@gmail.com on 8 Nov 2013 at 2:16