Ok, it's a fact that the memory will be reclaimed by the operating system on
program exit, but it's not nice to see all those memory leaks reported by
boundschecker on program exit ( i'am running under windows by the way ).
Suppose the server ran inside a program that added a watch variable to
problem though
delete mScheduler;
mEnv->reclaim();
delete mRtpPort;
delete mRtcpPort;
delete mRtpGroupsock;
delete mRtcpGroupsock;
}
-Original Message-
From: [EMAIL PROTECTED] on behalf of Luc Roels
Sent: Fri 6/29/2007 1:53 AM
To: [EMAIL PROTECTED]
Subject: [Live-devel] Ser
>One more question, what is the proper way to shutdown the LIVE555
>media server.
Just -C (or the "kill" command).
> The demo source just enters an endless loop
The "live555MediaServer" code (unlike the code for the application in
the "testProgs" directory) is not 'demo source'. It's the so
Hi Ross,
One more question, what is the proper way to shutdown the LIVE555 media server.
The demo source just enters an
endless loop, and if the program is forced to exit you get lots of memory
leaks. Could you enlight me with the proper
shutdown procedure?
___
