Broadcast Disconnect

Bug #1539119 reported by Jay Harvey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Expired
High
Unassigned

Bug Description

While broadcast Mixxx disconnects... and when you try to reconnected it says "Mixxx successfully connect to server", but it is not connected. Go to your stream server and you see no client is connected, try it connect again and nothing happens, no status messages as if to say "already connected", "successfully connected", "fail to connect", or "disconnected"

The only wait to back broadcasting again is to close and reopen MIxxx and reconnect then it works.

Tags: broadcast
Revision history for this message
Jay Harvey (jharveysxm) wrote :

Windows 10 64bit Intel core 3 with 4 gig of memory

Revision history for this message
Jay Harvey (jharveysxm) wrote :

sorry for Mixxx 2.0 64 bit

Revision history for this message
Daniel Schürmann (daschuer) wrote :

please post the mixxx.log file from a faulty run.

%APPDATA%\Mixxx\mixxx.log

If it is not your recent run, it may has a suffix like mixxx.log.5

Revision history for this message
Jay Harvey (jharveysxm) wrote :

See Attached

Revision history for this message
Jay Harvey (jharveysxm) wrote :

Not sure it is correct one, I had to restart to do my show

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Thank you, it was the right one

...
Debug [EngineShoutcast 1]: shout_queuelen 364
...
Debug [EngineShoutcast 1]: shout_queuelen 303031
Debug [EngineShoutcast 1]: EngineShoutcast::write() header error: -4 Socket error
...
Debug [EngineShoutcast 1]: EngineShoutcast::write() header error: -4 Socket error
Debug [EngineShoutcast 1]: EngineShoutcast::processDisconnect()
...
Debug [EngineShoutcast 1]: Connection pending. Waiting...
Debug [EngineShoutcast 1]: Streaming server made error: No error
Debug [EngineShoutcast 1]: EngineShoutcast::processConnect() socket error. Is socket already in use?

It looks like Mixxx does not release the socket after the socket error

Revision history for this message
Jay Harvey (jharveysxm) wrote :

Will their be resolution to this soon? I really need it Guys

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I am afraid not, sorry.
I have just digged through the Mixxx and the libshout 2.4.0 code, but I have not found anything suspicious.
Unfortunately I cannot reproduce this issue on Windows and I have no access to a windows machine to test this.
We need a Windows based contributor, who is able to reproduce the issue.

tags: added: shoutcast
Changed in mixxx:
importance: Undecided → High
Revision history for this message
Darren Smithson (darrenitu) wrote :

Hi- yes this is what happens to us- see my report https://bugs.launchpad.net/mixxx/+bug/1552312

Identical! It looks like a buffer overload due to a conflict with the latest update of Windows 10 and Mixxx V2. We are about to go 24/7 and were planning on using Mixxxx so please please please advise on a fix!!!

(64bit, 320kbps streaming, recording shows, 3 different laptops and configs but all W10)

Revision history for this message
Jay Harvey (jharveysxm) wrote :

This is also true for Linux. I changed all my systems from Windows and now I am using Linux Mint and The results are the same. If Mixxx disconnects while streaming, when you try to reconnect it prompts that you were reconnected, but when you check your streaming server you realize that Mixxx never reconnected and no matter how much times you try to reconnect from there on, it will never connect, until you restart Mixxx.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Hi Jay,

please provide the mixxx.log file from a run, where reconnecting has failed.
you will find it at ~/.mixxx/mixxx.log.x where ix is the number of Mixxx runs since then.

I have also prepared a Mixxx 2.1 alpha version that has additional debug messages.
https://launchpad.net/~nschloe/+archive/ubuntu/mixxx-nightly

If the issue still happens with this build, please post the mixxx.log as well.

Thank you.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

By the way: we have currently issues with our build server so we cannot provide a Windows 2.1 build.
If one can provide one, it would be great.

Revision history for this message
Daniel Schürmann (daschuer) wrote :
Revision history for this message
Sébastien BLAISOT (sblaisot) wrote :

the alpha build Daniel linked to has a bug and doesn't install in the right place. please use this new one instead: http://downloads.mixxx.org/builds/master/release/mixxx-2.1.0-alpha-pre-master-git5869-release-x64.exe

Revision history for this message
Marc Magon (gedmarc) wrote :

Hi There,

Is there any update? I'll be installing the 2.1 alpha now with pretty much the same environment.
Will post updates

Revision history for this message
Jay Harvey (jharveysxm) wrote :

on my last test with 2.1 I no such issue, but it never disconnected either

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Does this mean you have an other issue now?
Please describe it in a now bug. Thank you.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Any luck with 2.1.4 or 2.2.0 beta?

tags: added: broadcast
removed: shoutcast
Changed in mixxx:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mixxx because there has been no activity for 60 days.]

Changed in mixxx:
status: Incomplete → Expired
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8459

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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