linuxdcpp-team team mailing list archive

[Aoyagi Ritsuka <702602@xxxxxxxxxxxxxxxxxx>]

It was a memory-related error. Now it's working well.

If you're curious, here is some numbers: the queue consists of 321Gb in
347301 files. Being working with it linuxdcpp uses 1002Mb of RAM (and
that's way it were hit). It takes 3 minutes with 100% CPU usage for app
to start, during startup process the app window appears but is being
blank and grayed as "not responding", but in the end it starts and
everything is working fine.

Thanks for response! And thanks for linuxdcpp - is a nice software ;)

P.S. Here is a not interesting debug log. No errors, no crashes.
Everything is fine :)

** Attachment added: "gdb.txt"
   https://bugs.launchpad.net/linuxdcpp/+bug/702602/+attachment/1793438/+files/gdb.txt

-- 
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.
https://bugs.launchpad.net/bugs/702602

Title:
  App crashes on start with "big" (>3k files) downloads queue

Status in Linux DC++:
  Incomplete

Bug description:
  Detailed description of the issue:

  There is a problem with big downloads queue list handling.

  Now I'm trying to download around 2Gb (>3k) of photos from buddy with
  latest  LinuxDC++ version: 1.1.0~pre1~bzr (Ubuntu 10.10). After I've
  added a folder with all this files into queue, everything were fine,
  files were downloading and  ~/.dc++/Queue.xml is around 100Mb size.

  But when I closed app and then tried to re-open in, it utilized about
  100% CPU for 2-3 minutes and then crashed. After I've manually deleted
  ~/.dc++/Queue.xml and then restarted app and re-queued all files - it
  were working well, until next restart. So, it's just can't start with
  such a "huge" queue.

  Also I've noticed a periodical (every 5-10 seconds for 2-3 sec)
  overloads in moment with Queue.xml.tmp (around 39Mb) file
  creation/deletion:

  #top | grep linuxdcpp
  17851 ritsuka   21   1  658m 270m  14m S   41 13.5   1:51.36 linuxdcpp

  Of course, there is an easy solution for this case: do not add more
  than 1K files to queue at once. But isn't this limit too low? Maybe
  it's a bug?

  Steps to reproduce:
  - add a lot (>3k) of files to queue
  - close app
  - open app

  Expected results:
  Should handle it, probably? Or should not?

  Actual results:
  100% CPU for some time, than crashes.

  Version:
  tested on 1.1.0~pre1~bzr && 1.0.3

  OS:
  Ubuntu 10.10 Maverick x86_64 / 2.6.35-24-generic

  Hardware:
  Core 2 Duo 2.2GHz, 2Gb RAM

  Can provide my queue.xml list and/or any logs I have.