good, that clears plugins as a possible trigger for these crashes.
the next obvious suspect is user matching; attached is a patch that disables it. note that you will loose current user matching settings, so save them beforehand.
i have updated the boost atomic implementation in rev 3058. give it a try; it might help as it is often referenced in the crash logs.
since the crashes all seem to occur on reception of a message on an NMDC hub, it may be useful to try to isolate the originating hubs (if this is specific to a set of hubs at all, which might not be the case). it would also be interesting to know which messages were sent right before the crash.
good, that clears plugins as a possible trigger for these crashes.
the next obvious suspect is user matching; attached is a patch that disables it. note that you will loose current user matching settings, so save them beforehand.
i have updated the boost atomic implementation in rev 3058. give it a try; it might help as it is often referenced in the crash logs.
the next time you encounter a crash, try to follow <https:/ /answers. launchpad. net/dcplusplus/ +faq/1865> in order to get traces of all the running threads.
since the crashes all seem to occur on reception of a message on an NMDC hub, it may be useful to try to isolate the originating hubs (if this is specific to a set of hubs at all, which might not be the case). it would also be interesting to know which messages were sent right before the crash.