Crashes when connecting to server

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect to server
2. Wait about two minutes
3. Crash

What is the expected output? What do you see instead?
I expected to see my librari

What version of the product are you using? On what operating system?
8.5.1 and 8.6 on Froyo Nexus One over wifi

Please provide any additional information below.
My library has 24k songs, is it too large for DAAP-client?

Original issue reported on code.google.com by scottric...@gmail.com on 30 Aug 2010 at 4:18

[GoogleCodeExporter]

This may be too many songs.  If your server is public, could I access it to try 
and solve the problem.  If not, could you install the app "alogcat" and send me 
the log file.  This would let me know if it is too many songs.  People have had 
success with more though.  Thanks

Original comment by michael.miceli88@gmail.com on 30 Aug 2010 at 4:21

[GoogleCodeExporter]

I'm having the same problem... have approx 90k songs:

meta codes: 5508169923
No query/filter
Executing: select count(songs.id) from songs 
Number of results: 90881
Executing: select * from songs  limit 999999 offset 0
Enumerating size
Executing: select * from songs  limit 999999 offset 0
Got size: 13520945
Item enum:  got 90881 songs, dmap size: 13520945

Any chance you can make it limit the initial query to X songs?  Then grab more 
as they scroll?

I'll help if I can.

Original comment by thaman...@gmail.com on 2 Aug 2011 at 11:37

[GoogleCodeExporter]

I really wish I could, but the DAAP protocol doesn't allow it.  After logging 
in and obtaining songs, you can't get more later.  It's really unfortunate.

Original comment by michael.miceli88@gmail.com on 3 Aug 2011 at 12:15

[GoogleCodeExporter]

Hi.
Got the same problem (HTC Wildfire S, CM10, alpha2).
DAAP Server (Firefly svn-1696; about 100k songs)
I started to analys it with logcat.
First i startet the DAAP Client without any change.

OutputFile: logcat1

The problem is the small dalvikvm cache heapgrowlimit (default in my case 48mb).
You can check your dalvik setting in /system/build.prop
In my case:
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m

Dalvik is running out of free memory and throw an exception (and execute the 
daap-client).
So i tried to increase the dalvik heapgrowthlimit.

$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
$ vi /system/build.prop
and changed the heap grow limit to 75m (i startet with 96m but 75m should be 
enough)
dalvik.vm.heapgrowthlimit=75m
$ reboot

Then i tried and monitored it again:
OutputFile: logcat2

Now it works. In my case the daap prozess consumes up to 69127K.
This is a solution, but maybe the developers find an proper way to reduce the 
memory consumption.
nice day.

Original comment by fhifhi...@gmail.com on 22 Mar 2013 at 12:35

Attachments:

• logcat1.txt
• logcat2.txt

[GoogleCodeExporter]

update

Original comment by fhifhi...@gmail.com on 22 Mar 2013 at 12:44

Attachments:

• logcat1.txt