Comment 1 for bug 460093

Revision history for this message
Asheesh Laroia (paulproteus) wrote :

I just attempted to reproduce this. As far as I can tell, if Albert is right, just detaching and reattaching should grow the virtual memory map that is used as ctrlproxy's heap.

Step 1: Disconnect from ctrlproxy

(done in IRC client)

Step 2: run "pmap" to see the memory maps of the ctrlproxy process

paulproteus@rose:~ $ pmap $(pidof ctrlproxy) > /tmp/detached

Step 3: Wait 30 seconds

Step 4: Reattach to ctrlproxy

Step 5: run "pmap" to see the memory maps of the ctrlproxy process

paulproteus@rose:~ $ pmap $(pidof ctrlproxy) > /tmp/reattached

Step 6: Diff the two memory layout files

paulproteus@rose:~ $ diff /tmp/detached /tmp/reattached
5c5
< 0000000001866000 201260K rw--- [ anon ]
---
> 0000000001866000 209820K rw--- [ anon ]
109c109
< total 265916K
---
> total 274476K

You can see the files here, on the web: http://paulproteus.acm.jhu.edu/bug-report/2009-12-07/ctrlproxy/detached and http://paulproteus.acm.jhu.edu/bug-report/2009-12-07/reattached