Crash in NmdcHub "Line" callback

Bug #1266319 reported by ken snow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DC++
New
Undecided
Unassigned

Bug Description

I have read everything on this and nothing helps, this is the last thing that happened. Is there anyone at DC++ that can help? Or am I just wasting my time with DC++?

OK I split the hubs, here are the results

1st 5 hubs caused these crashes
###########################################
DC++ has crashed on 2014-01-02 at 21:52:01.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/atomicity.h (47)
DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/new_allocator.h (110), function: void/unknown execTasks(HubFrame* const this)
DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional (2029), function: bool dispatchAsync(Application* const this)

Information about the crash has been written.
###########################################
DC++ has crashed on 2014-01-02 at 11:00:04.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/bits/basic_string.h (716)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/NmdcHub.cpp (996), function: void/unknown on(NmdcHub* const this, string const& const aLine)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Speaker.h (60), function: void/unknown threadRead(BufferedSocket* const this)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/BufferedSocket.cpp (489), function: int run(BufferedSocket* const this)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Thread.h (110), function: DWORD starter(void/unknown p)

Information about the crash has been written.
###########################################
DC++ has crashed on 2014-01-01 at 13:37:19.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

DC++ has crashed on 2013-12-31 at 05:24:20.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

Failed to initialize the symbol handler (error: 998)

Information about the crash has been written.
###########################################
Second 4 hubs

Got this popup measage twice:
###########################################
Runtime Error!

Program: C:\Progams Files\DC++\DCPlusPlus.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
###########################################
and these crash logs
###########################################
DC++ has crashed on 2014-01-03 at 13:04:30.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

ntdll: [Failed to load the debugging data into memory (error: 2)] ?
DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/bits/unique_ptr.h (67), function: bool dispatchAsync(Application* const this)

Information about the crash has been written.
###########################################
DC++ has crashed on 2014-01-04 at 21:15:48.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

DCPlusPlus: ?
DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/bits/basic_string.h (1009), function: void/unknown onLine(NmdcHub* const this, string const& const aLine)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/NmdcHub.cpp (996), function: void/unknown on(NmdcHub* const this, string const& const aLine)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Speaker.h (60), function: void/unknown threadRead(BufferedSocket* const this)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/BufferedSocket.cpp (489), function: int run(BufferedSocket* const this)
DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Thread.h (110), function: DWORD starter(void/unknown p)
###########################################
Information about the crash has been written.

DC++ has crashed on 2014-01-05 at 02:12:45.
Please report this data to the DC++ team for further investigation.

DC++ version: DC++ v0.831 (r3365)
TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
Compiled with MinGW-w64's GCC 4.8.1
Exception code: c0000005
Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
Processors: 2 * x86

Writing the stack trace...

ntdll: [Failed to load the debugging data into memory (error: 2)] ?
DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/bits/unique_ptr.h (67), function: bool dispatchAsync(Application* const this)

Information about the crash has been written.
###########################################
and I got this from the user Temp folder
###########################################
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="DCPlusPlus.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="DCPlusPlus.exe" SIZE="7834126" CHECKSUM="0x565BF393" BIN_FILE_VERSION="0.8.3.1" BIN_PRODUCT_VERSION="0.8.3.1" PRODUCT_VERSION="0, 8, 3, 1" FILE_DESCRIPTION="DC++" PRODUCT_NAME="DC++" FILE_VERSION="0, 8, 3, 1" ORIGINAL_FILENAME="DCPlusPlus.exe" INTERNAL_NAME="DC++" LEGAL_COPYRIGHT="Copyright 2001-2013 Jacek Sieka" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x77D035" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="0.8.3.1" UPTO_BIN_PRODUCT_VERSION="0.8.3.1" LINK_DATE="11/11/2013 15:02:54" UPTO_LINK_DATE="11/11/2013 15:02:54" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="uninstall.exe" SIZE="150313" CHECKSUM="0x6A14CDE9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x60000" LINK_DATE="02/24/2012 19:19:59" UPTO_LINK_DATE="02/24/2012 19:19:59" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="991744" CHECKSUM="0x5ACBF35E" BIN_FILE_VERSION="5.1.2600.6293" BIN_PRODUCT_VERSION="5.1.2600.6293" PRODUCT_VERSION="5.1.2600.6293" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.6293 (xpsp_sp3_qfe.121001-1624)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFBE8A" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.6293" UPTO_BIN_PRODUCT_VERSION="5.1.2600.6293" LINK_DATE="10/03/2012 04:57:29" UPTO_LINK_DATE="10/03/2012 04:57:29" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

Revision history for this message
Fredrik Ullner (ullner) wrote :

The immediate thing that jumps out is that the PluginManager may have something to do with this. Do you have a plugin installed and enabled?

It looks like you are seeing this multiple times, so can you try and narrow down the hub that may generate this? E.g., disconnect from a couple of hubs and see if you get a crash. If you want, you can divulge the hub address(es) so we might also investigate the cause; we can mark this report as private (if you want), so only the developers see the information.

See also if you can try the steps provided in https://answers.launchpad.net/dcplusplus/+faq/578

By the way, other developers: PluginManager's destructor should be virtual... (It's a singleton so it shouldn't matter that much.)

summary: - DC++ has encountered a problem and needs to close
+ Crash in NmdcHub "Line" callback
description: updated
Revision history for this message
ken snow (ostinato32) wrote : RE: [Bug 1266319] Re: DC++ has encountered a problem and needs to close
Download full text (19.6 KiB)

Thanks so much for your replay. I started working on this with another person and they never returned any of my emails so I just stopped because I work full time and these things take a lot of time to work on. If you could give me a little more info about what you mean by a PluginManager? Do you mean a down load manager for window? A plug in for DC++? I don't remember installing anything but I will look more closely when I get home to the computer. I tried to keep as little software as possible off this Dell and to use it strictly for downloading from the internet. I had the same exact problem on the last computer a slower older Dell. I tried to find out what TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI is but could not find anything. If you reply to this email and I feel like you are going to really help I will then spend the time to try and segregate the hub or hubs that are causing this, if indeed that is the problem.
Ken

-----Original Message-----
From: "Fredrik Ullner" <email address hidden>
Sent: Friday, January 17, 2014 4:29pm
To: <email address hidden>
Subject: [Bug 1266319] Re: DC++ has encountered a problem and needs to close

The immediate thing that jumps out is that the PluginManager may have
something to do with this. Do you have a plugin installed and enabled?

It looks like you are seeing this multiple times, so can you try and
narrow down the hub that may generate this? E.g., disconnect from a
couple of hubs and see if you get a crash. If you want, you can divulge
the hub address(es) so we might also investigate the cause; we can mark
this report as private (if you want), so only the developers see the
information.

See also if you can try the steps provided in
https://answers.launchpad.net/dcplusplus/+faq/578

By the way, other developers: PluginManager's destructor should be
virtual... (It's a singleton so it shouldn't matter that much.)

** Summary changed:

- DC++ has encountered a problem and needs to close
+ Crash in NmdcHub "Line" callback

** Description changed:

 I have read everything on this and nothing helps, this is the last thing
 that happened. Is there anyone at DC++ that can help? Or am I just
 wasting my time with DC++?

-
 OK I split the hubs, here are the results

 1st 5 hubs caused these crashes
-
+ ###########################################
 DC++ has crashed on 2014-01-02 at 21:52:01.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Exception code: c0000005
 Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
 Processors: 2 * x86

 Writing the stack trace...

 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/atomicity.h (47)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/new_allocator.h (110), function: void/unknown execTasks(HubFrame* const this)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional (2029), function: bool dispatchAsync(Application* const this)

 Information about the crash has been written.
-
+ ###########################################
 DC++ has crashed on 2014-...

Revision history for this message
poy (poy) wrote :

no, PluginManager is not meant to be derived so its destructor not being virtual does not matter. ;) Singleton's destructor is, however, so PluginManager's destructor is as well anyway.

if anything, PluginManager (and other manager classes) could be marked as "final".

Revision history for this message
poy (poy) wrote :

for Ken: by "PluginManager", Fredrik is referring to DC++ plugins/extensions, the list of which can be accessed via Settings > Plugins (at the bottom). if you haven't installed any, chances are you don't have any.

Revision history for this message
ken snow (ostinato32) wrote : RE: [Bug 1266319] Re: Crash in NmdcHub "Line" callback
Download full text (8.5 KiB)

OK, thanks very much, I will look but pretty sure I never install any.

-----Original Message-----
From: "poy" <email address hidden>
Sent: Friday, January 17, 2014 5:34pm
To: <email address hidden>
Subject: [Bug 1266319] Re: Crash in NmdcHub "Line" callback

for Ken: by "PluginManager", Fredrik is referring to DC++
plugins/extensions, the list of which can be accessed via Settings >
Plugins (at the bottom). if you haven't installed any, chances are you
don't have any.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1266319

Title:
 Crash in NmdcHub "Line" callback

Status in DC++:
 New

Bug description:
 I have read everything on this and nothing helps, this is the last
 thing that happened. Is there anyone at DC++ that can help? Or am I
 just wasting my time with DC++?

 OK I split the hubs, here are the results

 1st 5 hubs caused these crashes
 ###########################################
 DC++ has crashed on 2014-01-02 at 21:52:01.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Exception code: c0000005
 Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
 Processors: 2 * x86

 Writing the stack trace...

 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/atomicity.h (47)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/new_allocator.h (110), function: void/unknown execTasks(HubFrame* const this)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional (2029), function: bool dispatchAsync(Application* const this)

 Information about the crash has been written.
 ###########################################
 DC++ has crashed on 2014-01-02 at 11:00:04.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Exception code: c0000005
 Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
 Processors: 2 * x86

 Writing the stack trace...

 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/bits/basic_string.h (716)
 DCPlusPlus: H:\Dev\DC++\0.831/dcpp/NmdcHub.cpp (996), function: void/unknown on(NmdcHub* const this, string const& const aLine)
 DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Speaker.h (60), function: void/unknown threadRead(BufferedSocket* const this)
 DCPlusPlus: H:\Dev\DC++\0.831/dcpp/BufferedSocket.cpp (489), function: int run(BufferedSocket* const this)
 DCPlusPlus: H:\Dev\DC++\0.831/dcpp/Thread.h (110), function: DWORD starter(void/unknown p)

 Information about the crash has been written.
 ###########################################
 DC++ has crashed on 2014-01-01 at 13:37:19.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Exception code: c0000005
 Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
 Processors: 2 * x86

 Writing th...

Read more...

Revision history for this message
eMTee (realprogger) wrote :

I don't know who/what and why removed the duplicate mark and the earlier comments from this bug but these crashes are the same we have been encountering for years. We have a few confirmed and 10's of expired reports of this.

I marked it as a duplicate of bug #1238966 because that's where we have some useful discussion of this problem and because the reported wasn't able to correctly answer my simple questions, instead, just demanding for a quick help for a problem we couldn't have been solved for years.

Specifically imo https://bugs.launchpad.net/dcplusplus/+bug/1238966/comments/3 is what would worth to investigate. The nature of various crashes and the years long inability to running a (slower) debug build under heavy load without hitting a specific assertion in the HubFrame that checks for the existence of the user pointer says to me that this can be a valid suggestion.

Revision history for this message
ken snow (ostinato32) wrote :
Download full text (9.7 KiB)

Thanks for your reply, but let me ask you, what is a heavy load? Do you consider having 10 files in your queue a heavy load? Being in 4 or 5 hubs a heavy load? Having 17000 files in you share a heavy load? I will be glad to help but I can not help when I don't get any answers to my questions. Just saying it is a duplicate of bug #1238966 doesn't help me. I read all of that and none of it help, some of it I don't even under stand. Duplicate Bug = easy way out. Sounds like DC++ is bugy and no one knows how to fix it.
Ken

-----Original Message-----
From: "eMTee" <email address hidden>
Sent: Friday, January 17, 2014 6:00pm
To: <email address hidden>
Subject: [Bug 1266319] Re: Crash in NmdcHub "Line" callback

I don't know who/what and why removed the duplicate mark and the earlier
comments from this bug but these crashes are the same we have been
encountering for years. We have a few confirmed and 10's of expired
reports of this.

I marked it as a duplicate of bug #1238966 because that's where we have
some useful discussion of this problem and because the reported wasn't
able to correctly answer my simple questions, instead, just demanding
for a quick help for a problem we couldn't have been solved for years.

Specifically imo
https://bugs.launchpad.net/dcplusplus/+bug/1238966/comments/3 is what
would worth to investigate. The nature of various crashes and the years
long inability to running a (slower) debug build under heavy load
without hitting a specific assertion in the HubFrame that checks for the
existence of the user pointer says to me that this can be a valid
suggestion.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1266319

Title:
 Crash in NmdcHub "Line" callback

Status in DC++:
 New

Bug description:
 I have read everything on this and nothing helps, this is the last
 thing that happened. Is there anyone at DC++ that can help? Or am I
 just wasting my time with DC++?

 OK I split the hubs, here are the results

 1st 5 hubs caused these crashes
 ###########################################
 DC++ has crashed on 2014-01-02 at 21:52:01.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Exception code: c0000005
 Windows version: major = 5, minor = 1, build = 2600, SP = 3, type = 1
 Processors: 2 * x86

 Writing the stack trace...

 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/atomicity.h (47)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/ext/new_allocator.h (110), function: void/unknown execTasks(HubFrame* const this)
 DCPlusPlus: h:/mingw/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional (2029), function: bool dispatchAsync(Application* const this)

 Information about the crash has been written.
 ###########################################
 DC++ has crashed on 2014-01-02 at 11:00:04.
 Please report this data to the DC++ team for further investigation.

 DC++ version: DC++ v0.831 (r3365)
 TTH: 7WYPILGP3DBQXRDZE7HHKR7INOZOJZBX4CG7AHI
 Compiled with MinGW-w64's GCC 4.8.1
 Excepti...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.