Ticket #9735 (closed defect: obsolete)
Winamp stops playing after more than 24 hours of running
|Reported by:||Rafcio||Owned by:|
Description (last modified by frank) (diff)
This seems like a resource leak problem and it's been there always (3.x.x? first version I tried). Here is the detailed description.
Host: Windows 7 x64 SP1
Guest: Windows XP Pro SP3
Winamp (latest version 5.621, much older version 5.24 tried with the same result) is configured for mp3 streaming (however with streaming turned off the same problem exists) using Icecast2 (v2.3.2) and Edcast (3.1.21). The mp3 files that Winamp plays are shared through VBox shared folder from the host. The audio is muted (it's meant for network streaming) and without a network traffic (streaming turned off for testing) the same problem happens. The problem is that after some time (AT LEAST 24 hours of continuous playing, but usually less than 48 hours) Winamp stops playing. It seems to respond to shut down (window closes), but it reamins in the task list and has to be killed. Restarting Winamp doesn't fix the problem. Winamp starts up, but it won't play anything at all. The VM (guest) has to be rebooted to clear the problem.
It seems to be a problem with a resource leak of some sort or some other limit reached (shared folder reaching transmission limit ;) ). It doesn't seem to be a problem with audio resources (because sound it is muted by Winamp) or a network resource limit (with or without network traffic same problem). Actually on the same host there is another XP guest running P2P client, transmitting copious amount of data daily and there is no problem whatsoever with that one. So networking issue can be safely excluded.
A physical box with almost identical configuration (with more stuff installed on the physical box) has no problem. Winamp streams mp3 music for weeks at at time without being touched at all. This proves that the configuration I have is sound (I've been streaming music for many years already) and the problem (whatever it is) is on the VBox side. Winamp is not to be blamed here.