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 the
doEventLoop to stop it and later start it again! Then you would need to
clean-up right? So the question was not which button to hit to exit the program
:-), but what the proper way is to clean-up and in what order? P.S. Sorry for
calling the media server a demo program :-) >One more question, what is the
proper way to shutdown the LIVE555
>media server.
Just <control>-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 source for
a complete application (product).
>, and if the program is forced to exit you get lots of memory leaks.
Not at all. Once any application ends (no matter how it ends), all
of its memory is reclaimed by the operating system. (Similarly, all
of its network sockets get closed.)
> Could you enlight me with the proper
>shutdown procedure?
Just kill it.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_________________________________________________________________
Ontdek Windows Live Hotmail, het ultieme online mailprogramma!
http://get.live.com/mail/overview
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
