On Sunday 30 September 2007 19:32, Melchior FRANZ wrote: > > I'm currenty investigating on the basis of a working theory > > that [...] > > I was so busy to defend my listeners, that I forgot to say: > thanks for investigating all that. It's a lot of work and quite > hard to do. All my attempts to find the cause failed so far.
You're welcome. :-) http://durktalsma.xs4all.nl/FlightGear/alloc-replaydata.png Here's actually the graph that forms the basis for my suspicion that memory management is involved. This is a plot of execution time of the code snippet stamp("Replay_01"); r = new FGReplayData; stamp("Replay_02"); based on a slightly modified version of the one I committed this afternoon. For the test, I didn't use the recycler, but created a new object for every frame. Currently I register about 15 fps, so in a runtime of about one hour, this code is executed about 54000 times. Of these 54000 calls to update(), approximately 1600 triggered a timing warning, and the results of these are plotted above. These results are quite puzzling: The majority of calls behave nicely finish executing within 10 ms. A few can actually take more than a second. Cheers, Durk ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
