Displaying 3 results from an estimated 3 matches for "omet".
Did you mean:
met
2011 May 09
1
You don't check for malloc failure
...sktop/server operating systems, don't do it.
Instead, icecast should keep its memory footprint low and avoid leaks at
all costs. Even with massive numbers of sources/clients, these 2 goals
alone should keep icecast under the OOM Killer's radar.
Here are a couple references:
http://blog.ometer.com/2008/02/04/out-of-memory-handling-d-bus-experience/
http://article.gmane.org/gmane.comp.audio.jackit/19998
Cheers,
R?mi
2011 May 07
3
You don't check for malloc failure
Hi,
> On Fri, 2011-04-29 at 09:05 +0200, Peter J. Philipp wrote:
>> You don't check for malloc failure. I've made a patch that is possibly
>> wrong but it saves the program from SIGSEGV and replaces it with SIGABRT.
On Fri, 29 Apr 2011, Philipp Schafft wrote:
> But I have a question:
> Not all of them (only had a brief look at the patch) look to be in a
>
2017 Mar 31
3
Well-formed @llvm.lifetime.start and @llvm.lifetime.end intrinsics
2017-03-31 13:46 GMT+02:00 Daniel Berlin <dberlin at dberlin.org>:
>
>
> On Fri, Mar 31, 2017 at 4:05 AM, Michael Kruse <llvmdev at meinersbur.de>
> wrote:
>>
>> 2017-03-31 1:16 GMT+02:00 Daniel Berlin <dberlin at dberlin.org>:
>> > if you transformed
>> >
>> > lifetime.start(%p)
>> > use %p
>> >