I can't see profile tab #126
Comments
|
Same here. node: 0.6.19, node-inspector: 0.2.0beta3, different browsers. |
|
Chiming in, same problem. Node 0.8.6 |
|
+1 I know its experimental and all, but followed instructions, and same here, no profiles tab/button anywhere |
|
Same problem. Tried downgrading to 0.1.10 and now I see the tab. |
|
I tried using 0.1.10 and don't see the profile tab. I also updated to chrome: Version 21.0.1180.89 Ubuntu 12.04 (154005) To see if I could find it, I opened up the console and there are many errors reported: Request with id = 3 failed. Profiler.causesRecompilation not implemented devtools.js:4151 |
|
Same for me with chrome version 21.0.1180.89, errors in chrome console and when I hit F5 I get errors from node-inspector itself: http.js:644 Mind you during install there were issues, can list if its useful but switching back to 0.1.10 did the job anyway. |
|
Same issue with chrome 22.0.1229.79, can't see |
|
Same issue on node 0.8.11. Downgrading to version 0.1.10, I get the following error when I try and take a heap snapshot as well: dyld: lazy symbol binding failed: Symbol not found: __ZNK2v813HeapGraphNode16GetDominatorNodeEv dyld: Symbol not found: __ZNK2v813HeapGraphNode16GetDominatorNodeEv |
|
+1 on node v0.8.14 |
|
The lack of commits/activity makes me think this project is dead? |
|
+1, yeap, looks like it's dead, we would have to find another tools to debug leaks it seems |
|
+1 |
|
Chrome: 23.0.1271.64 |
|
Any comments? @dannycoates |
|
+1 Details: I'm also getting the errors in the Chrome console: |
|
+1. 😒 |
|
+1 |
3 similar comments
|
+1 |
|
+1 |
|
+1 |
|
+1 (sadness) |
|
+1 :( |
|
+1 Ah well. |
|
This project seem to be dead now. Anyone figured out how to make it work? |
|
+1 :( |
|
+1 |
|
Yes, I'm afraid the profile tab here is dead. I've not been able to get the performance or stability to a useful level for anything beyond a trivial program, and I don't have the time to invest to get it working to my satisfaction. I also apologize for being so unresponsive to this thread, and all the other ones for that matter. I've been grievously derelict in my maintainer duties. You know when you want to just ignore something and hope it just goes away? It never works on the internet! Now, 6 months later(!), what can I say? Sorry, I'm an ass. It doesn't make me feel any better, but hopefully you can empathize and we can all move on and still be friends. On that note I resolve to at least tidy up the rest of these issues, pull requests and the code before I decide what to do with this project in the longer term. If you're at all interested in contributing to the project, please let me know. Thanks |
|
Alternatives? Anyone? Nodetime http://nodetime.com/ is not an option for me. |
|
I've heard that some people use valgrind, but to be honest, this seem to be dead-end to me |
|
c4milo/node-webkit-agent helped me track down a nasty leak this week, seems like a good fork of this project. |
|
I've done up a list of alternatives here for those interested: https://gist.github.com/balupton/3944017 |
|
I wonder whether @isaacs or @piscisaureus might be able to think of someone that could take the project over; this is one of the best debugging tools for NodeJS, it'd be a massive shame to see it die. |
|
There are forks that work - check my comment above. |
|
Danny, could you please let me know how to contribute to this project? Any terms? Thanks. |
|
You can still use node-inspector by downgrading as noted in some of the comments here. That is as easy as running "npm install node-inspector@0.1.10 -g". Prefix that with sudo as needed. |
|
Hey @dannycoates, how much money do you need to continue to support this project? If you setup a crowd-sourcing campaign I'd happily chip in. https://www.bountysource.com/ seems to work great for coding projects. For rewards you could do something like:
Just spit-balling with the rewards, whatever works. |
|
@dannycoates 👍 not a bad idea! I'm from the Bountysource team, we also offer merchandise fulfillment. If you went with @balupton's reward suggestions, we could print the shirts and mail em for you too. |
|
+1 On Fri, May 17, 2013 at 1:10 PM, ccvergara notifications@github.com wrote:
Martin Murphy |
|
+1 |
|
Chiefly commented: "c4milo/node-webkit-agent ...seems like a good fork of this project." |
|
+1 |
|
StrongLoop took up the challenge and got Danny's permission to maintain the project further on. Our first contribution was an upgrade to the latest Blink version of Developer Tools, please checkout the new version (0.3.x) to try the new UI yourself. See our blogpost for more information on the new features. |
|
@bajtos I've just taken a look and it looks awesome what you guys have done.. My only question is, why not release it on NPM? I have nothing against StrongLoop, but I definitely don't want to use their pre-packaged version of node.js, sorry! EDIT: I stand corrected; you have updated the NPM version! Gratz! 😄 |
|
the leak.js is crashed when i click the "take heap snapshot" button. |
|
I am afraid profiling is still not supported. See #185. |
|
+1 |
|
+1, also can't see the profile tab, with chrome 31.0.1650.63, node-inspector 0.7.4, node 0.10.26 |
|
+1, node-inspector 0.7.4, node 0.10.29, chrome 36.0 Is there a known working configuration? |
No. See #185 and related pull requests for the current work in progress. |
|
+1 |
|
+1 |
|
Please update to node-inspector 0.8.* to see profile tab. |
and others
node: 0.6.19
node-inspect: 0.2.0beta3
chrome: 21.0.1180.75
I can see script and console tabs, but can't see profile tab.
How can I open the profile tab?
The text was updated successfully, but these errors were encountered: