Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / lloyd/node-memwatch issues and pull requests
#88 - win64/node 14.15.3 can not install as deprecated c code
Issue -
State: open - Opened by dhlolo about 3 years ago
- 1 comment
#87 - Please mark as deprecated
Issue -
State: open - Opened by JaredCE almost 5 years ago
- 3 comments
#86 - Can't install on Win 10 with newer version of Python
Issue -
State: open - Opened by LeMoussel over 5 years ago
#85 - Cannot install memwatch on MacOS
Issue -
State: open - Opened by amaljose96 over 5 years ago
- 6 comments
#84 - Is this dead?
Issue -
State: closed - Opened by aichholzer over 6 years ago
- 2 comments
#83 - Where should I 'require' memwatch ?
Issue -
State: open - Opened by vadimJS about 7 years ago
#82 - installing Memwatch
Issue -
State: open - Opened by malipraful almost 8 years ago
- 6 comments
#81 - ubuntu install error
Issue -
State: open - Opened by cool-firer almost 8 years ago
- 4 comments
#80 - Install error
Issue -
State: open - Opened by narayanmp about 8 years ago
- 5 comments
#79 - [SOLVED] npm install error
Issue -
State: open - Opened by Nomia over 8 years ago
- 16 comments
#78 - Can I use memwatch browser side?
Issue -
State: open - Opened by halcwb over 8 years ago
#77 - Cannot find module './build/Release/memwatch'
Issue -
State: open - Opened by WebGuHui over 8 years ago
- 1 comment
#76 - added a section to the Readme to point to a newer (working in node 4.4) repo
Pull Request -
State: closed - Opened by jcollum almost 9 years ago
- 1 comment
#75 - Update release information in github
Issue -
State: closed - Opened by vicneanschi almost 9 years ago
- 1 comment
#74 - Module did not self register
Issue -
State: open - Opened by dvli2007 almost 9 years ago
- 4 comments
#73 - [discussion] [feature request] [help needed] Logging memory objects
Issue -
State: open - Opened by hellboy81 about 9 years ago
#72 - Incorrect License URL
Issue -
State: closed - Opened by sppatel about 9 years ago
#71 - memwatch-next doesn't build on node v5
Issue -
State: open - Opened by maritz over 9 years ago
- 8 comments
#70 - Just fixing a typo.
Pull Request -
State: open - Opened by shaialon over 9 years ago
#69 - Support Node.js 4.x
Issue -
State: closed - Opened by paulrutter over 9 years ago
- 11 comments
#68 - OSX install fails
Issue -
State: open - Opened by chisleu over 9 years ago
- 14 comments
#67 - can't install
Issue -
State: open - Opened by jimmywarting over 9 years ago
- 11 comments
#66 - unable to install memwatch in window 8.1 and 10
Issue -
State: open - Opened by VenkateshSrini over 9 years ago
- 1 comment
#65 - npm install memwatch-next fails
Issue -
State: open - Opened by reynot over 9 years ago
- 3 comments
#64 - io.js support?
Issue -
State: open - Opened by cworsley4 almost 10 years ago
- 9 comments
#63 - Installing on CentOS 6, node-gyp rebuild error
Issue -
State: open - Opened by furqansiddiqui almost 10 years ago
- 10 comments
#62 - Does not support on node.js v.0.12
Issue -
State: closed - Opened by smartmouse almost 10 years ago
- 24 comments
#61 - Is this module still alive?
Issue -
State: closed - Opened by goloroden about 10 years ago
- 6 comments
#60 - Fixed v8::IdleNotification for nodejs 0.12
Pull Request -
State: open - Opened by marcominetti about 10 years ago
- 21 comments
#59 - Memwatch failed to build with node v0.11.16
Issue -
State: open - Opened by jeremieca about 10 years ago
- 9 comments
#58 - HeapDiff() option to ignore sizes less than given parameter
Issue -
State: open - Opened by mariusa over 10 years ago
#57 - Use the bindings module for requiring native module
Pull Request -
State: open - Opened by vsacheti over 10 years ago
#56 - update using nan and v0.11 support added
Pull Request -
State: open - Opened by deepak1556 over 10 years ago
- 4 comments
#55 - Names of arrays and closures code (possible by demand) in HeapDiff
Issue -
State: open - Opened by AndyGrom over 10 years ago
#54 - Errors while installing memwatch on XP SP3
Issue -
State: open - Opened by nihalanig almost 11 years ago
- 1 comment
#53 - fix lib exporting if buildtype=debug
Pull Request -
State: open - Opened by drzhbe almost 11 years ago
#52 - Fails to build on node v0.11.13, Ubuntu 14.04
Issue -
State: open - Opened by karolyi almost 11 years ago
- 8 comments
#51 - Node JS on arm processor and debian OS (Node JS crashing on 50 % memory usage)
Issue -
State: open - Opened by aniruddhaMore about 11 years ago
#50 - Don't close handle scope in GC epilogue callback
Pull Request -
State: open - Opened by bnoordhuis about 11 years ago
- 1 comment
#49 - Module version mismatch
Issue -
State: open - Opened by yaru22 about 11 years ago
- 1 comment
#48 - build fails on windows vista visual c++ 2008 installed node 10.13
Issue -
State: open - Opened by jsdevel about 11 years ago
- 1 comment
#47 - Typo fix: aver => after
Pull Request -
State: open - Opened by nfriedly about 11 years ago
#46 - magic has no method 'upon_gc'
Pull Request -
State: open - Opened by dodo over 11 years ago
- 1 comment
#45 - Install fails on Ubuntu 12.04 32-bit
Issue -
State: open - Opened by amjibaly over 11 years ago
- 4 comments
#44 - Member Takesnapshot does not exist in Node 0.11.4
Issue -
State: open - Opened by arnaudbreton over 11 years ago
- 1 comment
#43 - Tracking the reference count to a particular type of objects
Issue -
State: open - Opened by sebpiq over 11 years ago
#42 - running example slightly_leaky.js does not generate any leak
Issue -
State: open - Opened by ziaaddils over 11 years ago
- 2 comments
#41 - How to read the heap diff?
Issue -
State: open - Opened by Broham over 11 years ago
#40 - Segfault on CentOS 6.3 64 bit
Issue -
State: open - Opened by mike-lang over 11 years ago
- 4 comments
#39 - Make 'leak' GC count configurable
Issue -
State: open - Opened by marklubi over 11 years ago
#38 - use node-bindings to support multi-platform deploy
Issue -
State: open - Opened by nickminutello over 11 years ago
#37 - Build fails @ Ubuntu 12.04
Issue -
State: open - Opened by yayscripting over 11 years ago
- 1 comment
#36 - Install fails on Mountain Lion with Node v0.10.5
Issue -
State: open - Opened by slowbrewedmacchiato almost 12 years ago
#35 - Fix build on osx mountain lion
Pull Request -
State: closed - Opened by bkw almost 12 years ago
- 3 comments
#34 - node-memwatch / examples / slightly_leaky.js: How to make it not leak?
Issue -
State: open - Opened by curana almost 12 years ago
- 3 comments
#33 - npm install fail on mac
Issue -
State: open - Opened by khwaja almost 12 years ago
- 3 comments
#32 - Fix uv_queue_work() call due to signature change in node v0.10
Pull Request -
State: closed - Opened by tmuellerleile almost 12 years ago
- 1 comment
#31 - npm update: error: no matching function for call to 'uv_queue_work'
Issue -
State: closed - Opened by webjay almost 12 years ago
- 1 comment
#30 - Assertion Failed: handle->InternalFieldCount > 0
Issue -
State: closed - Opened by dankuck almost 12 years ago
- 2 comments
#29 - Ship with pre-built binaries
Issue -
State: closed - Opened by scriby almost 12 years ago
- 3 comments
#28 - gc() method description
Pull Request -
State: closed - Opened by AurelienGasser almost 12 years ago
- 2 comments
#27 - cast to uv_after_work_cb for Node 0.10
Pull Request -
State: closed - Opened by rvagg about 12 years ago
- 5 comments
#26 - Conditional jump or move depends on uninitialised value(s)
Issue -
State: closed - Opened by strk about 12 years ago
- 3 comments
#25 - Sending STOP and CONT signals to a process triggers continuous "stats" event
Issue -
State: open - Opened by strk about 12 years ago
#24 - Tool Confusion
Issue -
State: closed - Opened by evantahler about 12 years ago
- 4 comments
#23 - See object content
Issue -
State: open - Opened by arcanis about 12 years ago
- 3 comments
#22 - Fix building on Windows
Pull Request -
State: closed - Opened by mscdex about 12 years ago
- 1 comment
#21 - memwatch.gc() requires --expose-gc
Issue -
State: open - Opened by feklee about 12 years ago
- 3 comments
#20 - Install fails in Ubuntu 12.04 (32 bit)
Issue -
State: closed - Opened by feklee about 12 years ago
- 3 comments
#19 - memwatch crashed on windows7
Issue -
State: closed - Opened by taichi about 12 years ago
- 1 comment
#18 - npm install fails on CentOS 5.7
Issue -
State: open - Opened by AndrewForth over 12 years ago
- 1 comment
#17 - "sed" breaks binding.gyp on windows
Issue -
State: closed - Opened by japj over 12 years ago
- 2 comments
#16 - possible crash bug if .end() is not called
Issue -
State: open - Opened by lloyd over 12 years ago
#15 - `memwatch` might be leaving heap snapshots around
Issue -
State: closed - Opened by brianloveswords over 12 years ago
- 2 comments
#14 - Support for windows
Pull Request -
State: closed - Opened by jmatthewsr-ms over 12 years ago
- 2 comments
#13 - npm install fails, node-gyp rebuild, windows
Issue -
State: closed - Opened by jmatthewsr-ms over 12 years ago
- 1 comment
#12 - Fix for Issue #11 - support for OSX x64
Pull Request -
State: closed - Opened by jhaynie over 12 years ago
- 2 comments
#11 - OSX runtime issue when using library
Issue -
State: closed - Opened by jhaynie over 12 years ago
- 2 comments
#10 - node 0.8 support
Issue -
State: closed - Opened by lloyd over 12 years ago
#9 - Added a readme
Pull Request -
State: closed - Opened by jedp over 12 years ago
#8 - Add timestamps to heapdiff data
Pull Request -
State: closed - Opened by jedp over 12 years ago
#7 - improve leak detection heuristics
Issue -
State: open - Opened by lloyd over 12 years ago
- 1 comment
#6 - write unit tests
Issue -
State: closed - Opened by lloyd over 12 years ago
#5 - include heapdiff in `leak` event
Issue -
State: open - Opened by lloyd over 12 years ago
- 1 comment
#4 - include "examples" in heapdiff
Issue -
State: open - Opened by lloyd over 12 years ago
#3 - write great docs
Issue -
State: closed - Opened by lloyd over 12 years ago
- 4 comments
#2 - implement 'leak' event
Issue -
State: closed - Opened by lloyd over 12 years ago
- 1 comment
#1 - Fix github URLs in package.
Pull Request -
State: closed - Opened by bluesmoon almost 13 years ago