| View previous topic :: View next topic |
| Author |
Message |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Mon Oct 18, 2010 11:31 am Post subject: Malloc error |
|
|
Hi,
in the last few days I'm experiencing a problem with icecast server.
Sometimes it doesn't answer , streams stop and I see this error on the log file:
WARN Memory allocation failed : xmlEncodeEntitiesReentrant: malloc failed
I'm using icecast 2.3.2 on a Windows 2008 x64 server with 8GB of ram.
Could you help me?
thanks
Dave |
|
| Back to top |
|
 |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Mon Oct 18, 2010 3:52 pm Post subject: |
|
|
This is an update about my problem.
I have Icecast 2.3.2 on 2 windows server 2008 x64 and on both server icecast is using a great amount of memory and they are growing.
On one server it's at 1.2GB ram.
On the second server Icecast it's started 5 hours ago and now it is at 170MB of ram.
On a third server with Windows 2003 x32 the icecast process is at only 100MB.
Is there a problem with x64 windows architecture or with windows 2008?
Thanks for any help
Dave
Last edited by Dave18 on Mon Oct 18, 2010 7:57 pm; edited 1 time in total |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 18, 2010 5:15 pm Post subject: |
|
|
I suspect it's a reference mismatch causing the queues to explode, can you try the win32 trunk build on my website. It should fix a few cases.
karl. |
|
| Back to top |
|
 |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Mon Oct 18, 2010 7:38 pm Post subject: |
|
|
Karl,
thanks for your answer, but ... where is the win32 trunk build on your web site?
I'm very sorry I'm not able to find it.
Dave
Last edited by Dave18 on Mon Oct 18, 2010 7:57 pm; edited 1 time in total |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 18, 2010 7:40 pm Post subject: |
|
|
Right under Main releases. Where it says
"Trunk build 01/06/2010 win32"
karl. |
|
| Back to top |
|
 |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Mon Oct 18, 2010 7:58 pm Post subject: |
|
|
thanks Karl, found it!
I'm going to install this version and I'll let to know how the memory will goes.
Can I use the actual 2.3.2 xml config file or there is something that I've to change?
Dave |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 18, 2010 8:07 pm Post subject: |
|
|
no changes to the xml are required
karl. |
|
| Back to top |
|
 |
Ant
Joined: 11 Jun 2008 Posts: 27 Location: Russia
|
Posted: Tue Oct 19, 2010 12:47 pm Post subject: |
|
|
| karlH wrote: |
Right under Main releases. Where it says
"Trunk build 01/06/2010 win32"
karl. |
Do not be angry, but is there any developing roadmap?
I'am asking because it's intresting is there any plans about releasing some stable icecast version in this year? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Oct 19, 2010 1:22 pm Post subject: |
|
|
I've been busy with other things which has prevented me getting back to the trunk code. The kh tree seems to be at a point where I don't need to keep coming back to it now and we really should focus on a 2.3.3 at the very least.
Feedback on cases like the memory leak as reported by the original poster would be a good but sometimes it can take a while for these cases to trigger. I've identified a couple more rare cases than need plugging up. Overall I was wanting 2.3.3 to be mainly a fixes release, the worker thread changes are more extensive and was going to wait until later for those.
karl. |
|
| Back to top |
|
 |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Wed Oct 20, 2010 8:07 am Post subject: |
|
|
Karl,
I confirm that my problem is solved with the trunk version you gave me.
After 36 hours on both windows 2008 x64 server icecast is using only 7 MB.
Thanks a lot for your help and for your job.
Dave |
|
| Back to top |
|
 |
Ant
Joined: 11 Jun 2008 Posts: 27 Location: Russia
|
Posted: Wed Oct 20, 2010 8:23 am Post subject: |
|
|
| karlH wrote: |
I've been busy with other things which has prevented me getting back to the trunk code. The kh tree seems to be at a point where I don't need to keep coming back to it now and we really should focus on a 2.3.3 at the very least.
Feedback on cases like the memory leak as reported by the original poster would be a good but sometimes it can take a while for these cases to trigger. I've identified a couple more rare cases than need plugging up. Overall I was wanting 2.3.3 to be mainly a fixes release, the worker thread changes are more extensive and was going to wait until later for those.
karl. |
Thanks for info. Mainly i don't search for new features, i'am happy with featureset of 2.3.2, i'am intrested in stability issue (memory leak 12 days - 300mb already eated) and some little bug like disappearing relay mountpoints if on-demand option is enabled. |
|
| Back to top |
|
 |
Dave18
Joined: 26 Jan 2010 Posts: 20
|
Posted: Wed Oct 20, 2010 10:48 pm Post subject: |
|
|
Karl,
I've found something I can't understand with the trunk version.
Icecast is working but it doesn't write any log files.
I'm using the same xml from the previous 2.3.2 installation.
To use the trunk version I have done these steps:
1. I've renamed the 2.3.2 icecast folder
2. I've installed the trunk version
3. I've saved the default xml config file and I've copied the xml config file used on my previous 2.3.2 version.
I've checked the permissions on the new icecast folder and USERS can do everything on that folder.
To confirm this I see the pid file written from icecast.
The xml configuration is this:
<paths>
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<pidfile>./icecast.pid</pidfile>
<alias source="/" dest="/status.xsl"/>
</paths>
./web and ./admin ./icecast.pid are working.
So I've looked at your default xml file:
<paths>
<logdir>c:\xiph\logs</logdir>
<webroot>../web</webroot>
<adminroot>../admin</adminroot>
<alias source="/" dest="/status.xsl"/>
</paths>
I've solved the problem using an absolute path like you (I've used c:\icecast\logs), but why ./logs doesn't work?
Another question is about your ../web and ../admin: are they right?
I didn't tryed to use the default xml file, but maybe ../web and ../admin are not right.
Or I'm doing some confusion?
I've tried on 2 different servers with the same result.
I've solved the problem of the log files, but I'd like to give you this information.
Thanks
Dave |
|
| Back to top |
|
 |
|