You are here: Home » Topic » svn 1696 Crashing after a request from MediaElement (WPF)

svn 1696 Crashing after a request from MediaElement (WPF)

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server General Discussion svn 1696 Crashing after a request from MediaElement (WPF)

This topic contains 3 replies, has 2 voices, and was last updated by  EVILRipper 8 years, 6 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #2836

    thimp

    Hi All,
    Since this is my first time posting, let me start with giving my compliments to firefly and the development effort to make it all happen! I do love the speed and ease of use of this server which I run on my Synology DS207+ NAS device (for streaming music around the house) and on my Windows Vista machine (for development).

    I’m currently developing a WPF (and soon to come Silverlight) client for FireFly. I m planning to publish the classes and application one of these day’s –let me do some clean up 🙂 —

    In the mean time I have a slight problem: I can consistently crash my mt-daapd demon on the DS207+ (build = svn 1696) by requesting a song. The level 9 log tells me:

    2008-12-23 21:36:49 (0000c002): Got listen socket 13
    2008-12-23 21:36:49 (00134003): Thread 73:
    2008-12-23 21:36:49 (00134003): Request: GET /rsp/stream/6667 HTTP/1.1
    2008-12-23 21:36:49 (00134003): Thread 73: Read: Accept: */*
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *Accept=*/**
    2008-12-23 21:36:49 (00134003): Added *Accept=*/**
    2008-12-23 21:36:49 (00134003): Thread 73: Read: User-Agent: NSPlayer/11.0.6001.7001
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *User-Agent=NSPlayer/11.0.6001.7001*
    2008-12-23 21:36:49 (00134003): Added *User-Agent=NSPlayer/11.0.6001.7001*
    2008-12-23 21:36:49 (00134003): Thread 73: Read: Host: san
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *Host=san*
    2008-12-23 21:36:49 (00134003): Added *Host=san*
    2008-12-23 21:36:49 (00134003): Thread 73: Read: X-Accept-Authentication: Negotiate, NTLM, Digest, Basic
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *X-Accept-Authentication=Negotiate, NTLM, Digest, Basic*
    2008-12-23 21:36:49 (00134003): Added *X-Accept-Authentication=Negotiate, NTLM, Digest, Basic*
    2008-12-23 21:36:49 (00134003): Thread 73: Read: Pragma: version11-enabled=1
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *Pragma=version11-enabled=1*
    2008-12-23 21:36:49 (00134003): Added *Pragma=version11-enabled=1*
    2008-12-23 21:36:49 (00134003): Thread 73: Read: Pragma: no-cache,rate=1.000,stream-time=0,stream-offset=0:0,packet-num=4294967295,max-duration=0
    2008-12-23 21:36:49 (00134003): Thread 73: Adding header *Pragma=no-cache,rate=1.000,stream-time=0,stream-offset=0:0,packet-num=4294967295,max-duration=0*
    2008-12-23 21:36:49 (00134003): Updating Pragma from version11-enabled=1 to no-cache,rate=1.000,stream-time=0,stream-offset=0:0,packet-num=4294967295,max-duration=0
    2008-12-23 21:36:49 (00134003): Thread 73: Out of memory
    2008-12-23 21:36:49: Aborting
    2008-12-23 21:36:49 (00004000): Rendezvous socket closed (daap server crashed?) Aborting.
    2008-12-23 21:36:49: Aborting

    On my vista i have Version svn-1586 running and it does not crash.

    I request the stream from a MediaElement (which encapsulates a windows mediaplayer OCX, I believe) by setting the Source to:
    “mms://myname:[email protected]:3689/rsp/stream/6667”.

    I could not find any reference to this problem. Does anyone have a hint to a solution?

    Thanks, Thimp

    #18295

    EVILRipper
    Participant

    The log clearly states it dies due to “Out Of Memory”.
    Though to me this merely sounds like an effect from a completely different cause.
    Let’s see if I can recreate it.

    You just crashed my music!
    And the RSP URL should be fine. I don’t think you need the username and password though.
    I’m sorry. I have no idea..

    #18296

    anders
    Participant

    I’m also getting this message. But I can’t see why. First of all it occurs many times a day, with no specific pattern. It only happens when I skip to the next song on the playlist. It crashes with no reason. No full harddrives and no other heavily processes currently running at the same time. The disk drive only used to my music library. It’s quite annoying because I allways have to ssh in to my Fedora box and start the mt-daapd whenever it happens. And my music stops playing and iTunes often locks up until it has tested every song left in the list before it stops and starts responding again. In most cases leading to force quit the application (Windows version of iTunes of course).

    This is though the only problem I’m having with the media server, else it works as nothing ever have worked before and I’m very satisfied with it while it ain’t crashing.

    A printout of my mt-daapd.log:

    2009-01-04 18:05:49 (b5bfeb90): Session 0: Streaming file ’05Tired of Waiting for You.flac’ to 10.0.0.2 (offset 0)
    2009-01-04 18:05:51 (b7fa2a20): Got CLD signal. Reaping
    2009-01-04 18:08:19 (b7fa2a20): Got CLD signal. Reaping
    2009-01-04 18:08:19 (b5bfeb90): Session 0: Streaming file ’06Everybody’s Gonna Be Happy.flac’ to 10.0.0.2 (offset 0)
    2009-01-04 18:08:42 (b7fa2a20): Rendezvous socket closed (daap server crashed?) Aborting.
    2009-01-04 18:08:42: Aborting

    I’m running version svn-1586. Is it recommanded that I upgrade btw? Is there any newer versions out? I hate using a lot of time on such things, I’m happy when it works and else I don’t do any changes until I have to. Like now.

    Thanks for any help 🙂

    #18297

    EVILRipper
    Participant

    svn-1586 is one of the most stable nightlies. So I don’t think upgrading would fix anything.
    The log gives you no clue what is causing the crash.
    Try raising the debuglevel in your config file up to 9.
    That way your log file will be more specific when crashing.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.