This repository was archived by the owner on Jan 6, 2020. It is now read-only.

Maid 22 bad alloc#14

Open

ned14 wants to merge 15 commits into

maidsafe-archive:nextfrom

ned14:MAID-22_bad_alloc

Commits on Aug 27, 2014

log messages for tracking down the bad_alloc issue
maqi
committed
avoiding mis-handling as symmetric NAT when running multiple vaults on same machine
maqi
committed
log around remove socket
maqi
committed
temp fix to the socket thread safe issue
maqi
committed
minor style correction
maqi
committed
reduce logs
maqi
committed
try to catch certain serious system exception as well
maqi
committed
Revert "try to catch certain serious system exception as well"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "reduce logs"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "minor style correction"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "temp fix to the socket thread safe issue"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "log around remove socket"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "avoiding mis-handling as symmetric NAT when running multiple vaults on same machine"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Revert "log messages for tracking down the bad_alloc issue"
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed
Backed out my original change to make Dispatcher not get deleted while it is being used in favour of Transport::Close() dispatching the connection teardown onto the appropriate ASIO thread instead.
Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com)
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Maid 22 bad alloc#14

Maid 22 bad alloc#14
ned14 wants to merge 15 commits into
maidsafe-archive:nextfrom
ned14:MAID-22_bad_alloc

Commits on Aug 27, 2014

log messages for tracking down the bad_alloc issue

avoiding mis-handling as symmetric NAT when running multiple vaults on same machine

log around remove socket

temp fix to the socket thread safe issue

minor style correction

reduce logs

try to catch certain serious system exception as well

Revert "try to catch certain serious system exception as well"

Revert "reduce logs"

Revert "minor style correction"

Revert "temp fix to the socket thread safe issue"

Revert "log around remove socket"

Revert "avoiding mis-handling as symmetric NAT when running multiple vaults on same machine"

Revert "log messages for tracking down the bad_alloc issue"

Backed out my original change to make Dispatcher not get deleted while it is being used in favour of Transport::Close() dispatching the connection teardown onto the appropriate ASIO thread instead.