[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #12 from Gabriel Wicke gwi...@wikimedia.org --- A dsh command to list memory of all node processes in rt testing (from https://www.mediawiki.org/wiki/Parsoid/Round-trip_testing#Some_dsh_tricks): dsh -M -cf /home/gwicke/rtclients ps

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-07 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #10 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 105875 merged by jenkins-bot: Bug 58952: Help incremental GC further by breaking refs https://gerrit.wikimedia.org/r/105875 -- You are receiving this mail

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-06 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 Gerrit Notification Bot gerritad...@wikimedia.org changed: What|Removed |Added Status|NEW

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-06 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #9 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 105875 had a related patch set uploaded by GWicke: WIP Bug 58952: Help incremental GC further by breaking refs https://gerrit.wikimedia.org/r/105875 -- You are

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Priority|Unprioritized |High --- Comment

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 Gabriel Wicke gwi...@wikimedia.org changed: What|Removed |Added Status|PATCH_TO_REVIEW |NEW -- You are

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #7 from ssas...@wikimedia.org --- Hmm ... okay .. so, I guess it looks like we have to do a direct upgrade to 0.12 instead then unless we get a reliable workaround with the --max_old_space_size param. -- You are receiving this

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2014-01-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #8 from Gabriel Wicke gwi...@wikimedia.org --- Also possibly relevant: The LATENCY AND IDLE GARBAGE COLLECTION paragraph in http://blog.nodejs.org/2013/03/11/node-v0-10-0-stable/ -- You are receiving this mail because: You are on

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-26 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #3 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 103756 had a related patch set uploaded by GWicke: Bug 58952 WIP: Try to make sure env and old documents are freed early https://gerrit.wikimedia.org/r/103756 --

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-26 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #4 from ssas...@wikimedia.org --- Actually, on some of these pages, it looks like at least in RT testing, diff classification is the culprit. Same behavior on node 0.8.26, node 0.10.19,and node 0.10.24. -- [subbu@earth

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-26 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #5 from ssas...@wikimedia.org --- It looks like jsdiff is the culprit at least in rt-testing for inefficient processing of some pages -- main cause for both long processing times + memory usage (peak 2.3g virtual, 1.3g resident) on

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-24 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #1 from ssas...@wikimedia.org --- Another: enwiki:Russia_at_the_2004_Summer_Olympics in 35387 ms -- You are receiving this mail because: You are on the CC list for the bug. ___

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-24 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 --- Comment #2 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 103639 had a related patch set uploaded by GWicke: Bug 58952: Avoid repeated require of Util from defines https://gerrit.wikimedia.org/r/103639 -- You are

[Bug 58952] node 0.10 memory leak / lockup of client (possible test cases)

2013-12-24 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=58952 Gerrit Notification Bot gerritad...@wikimedia.org changed: What|Removed |Added Status|NEW