This appears to be a consequence of the boost futures. Is there anyway to avoid the high number of stacks required?
Any chance you could dig deeper by running the client under valgrind
memcheck to possibly find out more?
Another test: rip out everything from the client but the establishment
of the connection (up to onjoin) and let the client just sit still.
21682: ./callee -r myrealm -p 8888
00010000 316K r-x-- callee
0006e000 4K r---- callee
0006f000 4K rw--- callee
00070000 148K rw--- [ anon ]
b4a00000 4K ----- [ anon ]
b4a01000 8188K rw--- [ anon ]
b5200000 4K ----- [ anon ]
b5201000 8188K rw--- [ anon ]
b5a00000 4K ----- [ anon ]
b5a01000 8320K rw--- [ anon ]
b6221000 892K ----- [ anon ]
b6389000 4K ----- [ anon ]
b638a000 8188K rw--- [ anon ]
b6b89000 412K r-x-- libm.so.6
I also ran callee under Ubuntu (x86_64) and it shows the same stack pattern and some other very large memory requirement (this is the original callee source code):
0000000000400000 492K r-x-- callee
000000000067a000 4K r---- callee
000000000067b000 4K rw--- callee
000000000067c000 4K rw--- [ anon ]
0000000002506000 200K rw--- [ anon ]
00007fd216ffe000 4K ----- [ anon ]
00007fd216fff000 8192K rw--- [ anon ]
00007fd2177ff000 4K ----- [ anon ]
00007fd217800000 8192K rw--- [ anon ]
00007fd218000000 132K rw--- [ anon ]
00007fd218021000 65404K ----- [ anon ]
00007fd21c186000 4K ----- [ anon ]
00007fd21c187000 8192K rw--- [ anon ]
00007fd21c987000 4K ----- [ anon ]
00007fd21c988000 8192K rw--- [ anon ]
00007fd21d188000 4K ----- [ anon ]
00007fd21d189000 8192K rw--- [ anon ]
00007fd21d989000 1056K r-x-- libm-2.23.so
Yet another: do you see the same when the caller/publisher/subscriber
(rather the callee)?
Cheers,
/Tobias
Hi Chris,
right now, I am at a conference (until monday), so unfort. wont be able to look. Maybe you could file an issue and ping/CC the Bonefish guys within the issue? They are also very familiar with the AutobahnCpp codebase (contributed lots of code) ..
Cheers,
/Tobias
Sent from Mobile (Google Nexus 5)
I've started working with cppWamp and it doesn't have stack problems, but it isn't using boost futures which I think is the source of the stack problem.I would prefer to use Autobahn-cpp so let me know if there is additional information I can provide to help with the investigation.
--
You received this message because you are subscribed to the Google Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autobahnws+unsubscribe@googlegroups.com.
To post to this group, send email to autob...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autobahnws/d538488b-9b25-40d6-892a-133f208da2de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.