Hi, Evert Vorster wrote > Hi there.. > > I pretty much narrowed it down to my system running out of memory. I was > watching the amount of memory left on gkrellm, and when it got down to > about > 1Gb free openmovieeditor crashed. > Now I have shortened the movie to about 5 minutes and less source > material, > it renders fine.
Of course one should always check if a malloc succeeded, but the following sentences in the malloc manpage prevented me from doing this by now: ============ 8< ============================ BUGS By default, Linux follows an optimistic memory allocation strategy. This means that when malloc() returns non-NULL there is no guarantee that the memory really is available. This is a really bad bug. ============ 8< ============================ Does someone know how to workaround this from within a program (i.e. without using sysctls)? I have no idea how Openmovieeditor opens the files (all at once or on demand during rendering). The latter strategy could possibly work around the problem but would be harder to implement. Maybe Richard can provide some insight. Burkhard ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Gmerlin-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gmerlin-general
