linuxdcpp-team team mailing list archive

[poy <1029629@xxxxxxxxxxxxxxxxxx>]

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.

** Patch added: "nousermatch.patch"
   https://bugs.launchpad.net/dcplusplus/+bug/1029629/+attachment/3323042/+files/nousermatch.patch

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1029629

Title:
  Crash with r3013

Status in DC++:
  New

Bug description:
  I can't really give detailed information about this, I didn't do anything special when the crash occured.
  Please find the crash log attached. I assume that it has not been fixed in the 2 newer releases.

  If you need anything else from my side regarding this, let me know
  about it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1029629/+subscriptions