Closed GoogleCodeExporter closed 8 years ago
Sorry, i've been klicking the enter-key accidentally too early. Here's the info:
I choose the own cachegrind.out-File (webgrind/index.php). This will bring my
apache
to 100% cpu and never ending call.
Maybe the tool shouldn't offer the profile for his own file.
Original comment by micha.be...@googlemail.com
on 22 Jul 2008 at 8:40
Thought I fixed this. Are you using the latest version (0.81)?
Original comment by oett...@gmail.com
on 22 Jul 2008 at 7:31
Hi. Yes i'm using 0.81.
Here's the pirst part from Changelog.txt:
#summary Changelog for webgrind.
==0.81==
* Fixed: Potential infinite loop. (issue 12)
Original comment by micha.be...@googlemail.com
on 22 Jul 2008 at 7:50
Hi,
Sorry about the lack of activity from my part. I am on vacation, will look into
this
in september.
Original comment by oett...@gmail.com
on 19 Aug 2008 at 5:03
I've identified the problem to be with the refresh button. Only then does the
self profile appear. It is correctly
filtered when first loading the page.
Will investigate.
Original comment by gugakf...@gmail.com
on 20 Aug 2008 at 8:13
Scratch that, I am in fact unable to reproduce. There are measures to avoid
this, so I'm not sure how this
happens.
Original comment by gugakf...@gmail.com
on 20 Aug 2008 at 8:51
I am also unable to reproduce.
Have made a small alteration in r133 that could affect the issue. Could you
test with this revision?
Original comment by oett...@gmail.com
on 26 Aug 2008 at 12:08
Issue has occured with me, webgrind 0.81
Ubuntu 8.10
Php 5.2.6
I can see the webgrind caches in the drop down box and when selected, kills the
server completly.
Cachgrinds filenames in /tmp look like this:
cachegrind.out.2268 cachegrind.out.2725.webgrind
cachegrind.out.2270 cachegrind.out.2726
Mabe just set that dropdown box not to load .webgrind in the dropdown ?
Its said above fixes are in place for this but don't know what they are ?
Original comment by tom.baby...@googlemail.com
on 12 Sep 2008 at 9:42
forgot to add, xdebug Version 2.0.3
Original comment by tom.baby...@googlemail.com
on 12 Sep 2008 at 9:42
Output of Webgrind_FileHandler in the __construct of $files directly before the
usort
and $this->files = $files looks like this on my pc:
[cachegrind.out.2769] => Array
(
[absoluteFilename] => /tmp/cachegrind.out.2769
[mtime] => 1221253060
[preprocessed] =>
[invokeUrl] => /home/ntom/www/webgrind/index.php
)
As you can see, the invokeUrl is the webgrind index.php, my original comment
noting
the cachegrind.out.2725.webgrind would mean files generated by
webgrind/index.php
would be generating those name suffixs but maybe not on my system.
Running 'diff cachegrind.out.2769 cachegrind.out.2769.webgrind' reveals both to
be
the same file.. ?
Open to idea's but what is the deal here?
Original comment by tom.baby...@googlemail.com
on 12 Sep 2008 at 9:52
This affected me in release 1.0.
I have changed line 99 of Handler.php from that release from:
$invokeUrl = $this->getInvokeUrl($absoluteFilename);
to:
$invokeUrl = rtrim($this->getInvokeUrl($absoluteFilename));
This seems to have fixed the problem for me (there was some white space in
$invokeURL).
Original comment by testingp...@googlemail.com
on 1 Mar 2010 at 3:49
Hopefully fixed in r164
Original comment by gugakf...@gmail.com
on 5 Jul 2010 at 11:20
Original comment by gugakf...@gmail.com
on 24 Jan 2011 at 12:21
Original issue reported on code.google.com by
micha.be...@googlemail.com
on 22 Jul 2008 at 8:33