bugmldonkey, a multi-networks file-sharing client - Bugs: bug #12504, Core crashes after 30 mins

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #12504: Core crashes after 30 mins

Submitted by:  Jochen Kokemüller <jkon>
Submitted on:  Tue 29 Mar 2005 08:17:49 PM UTC  
 
Category:  Core Severity:  3 - Normal
Item Group:  Program malfunction Status:  Invalid
Assigned to:  None Open/Closed:  Closed
Release:  Release:  2-5-30-1
Operating System:  Linux Binaries Origin:  CVS / Self compiled
CPU type:  Intel x86

Thu 31 Mar 2005 08:28:19 AM UTC, comment #5: 

I suppose this was a blend of home-made problems and bug #12384.
Together with the patch mentioned in that bug it is now working fine.

Jochen Kokemüller <jkon>
Wed 30 Mar 2005 07:20:58 PM UTC, comment #4: 

It is:

buildinfo

... without underscore ... at least it is this way in the CVS-versions, not sure if the SVN versions differ here.

Fritz Mock <surround>
Wed 30 Mar 2005 03:11:18 PM UTC, comment #3: 

it's an internal mldonkey command. enter it where you enter all the other mldonkey commands (like dllink etc...).

are you sure the core crashes and does not just hang?

Amorphous <amorphous>
Wed 30 Mar 2005 11:53:52 AM UTC, comment #2: 

This time i don't get any entries in the system logs, so i suppose this is a different issue then bug #12489.

Where do i execute build_info? i could not find any place to do so.

Jochen Kokemüller <jkon>
Wed 30 Mar 2005 10:20:57 AM UTC, comment #1: 

i asume the oom killer does not take care of mldonkey, as you described it in savannah bug #12489 ?

please paste the output of the mldonkey command build_info .

Amorphous <amorphous>
Tue 29 Mar 2005 08:17:49 PM UTC, original submission:  

On my low-profile system:
PII 400MHz
128MB Ram
300MB Cache
Linux Debian sarge

the core crashes always about 30 mins after startup. Unfortunatly it does not give me any hint on why it chrashes, but it doesn't state SIGSEGV.
I'm logging already a whole bunch of things but neither in the log file there is a hint on why the crash occurs.

I started mldonkey with Bittorent and/or the edonkey plugin, but it didn't change anything. All other plugins are disabled.

If you give me any hint on how to support you with more descent debug info, i.e. which log mode to activate, i will be pleased to do so.

Jochen Kokemüller <jkon>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

 

 

Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-03-31 amorphous StatusNone => Invalid
    Open/ClosedOpen => Closed

Back to the top


Powered by Savane 3.5