[osg-users] OpenSceneGraph-3.6.5 release candidate 2 tagged, please test

OpenSceneGraph Users osg-users at lists.openscenegraph.org
Mon Jan 27 14:32:10 PST 2020

Hi Robert,

As I've mentioned in the past, I'm an OpenMW (note the single M) developer. 
It was actually me who reported the issues with the default font, and only 
a subset were resolved before you went on hiatus. I've lost the thread 
where we were discussing it as I'd bookmarked the forum thread, which is 
now dead. As I recall, though, my most recent minimal 
things-don't-get-relased-when-they-should example was resolvable by a 
couple of potential changes I suggested, but you said they'd have to wait 
until you could investigate more thoroughly, as it was in code no one had 
touched for a while, so could maybe upset other applications, or not 
exhaustively remove all such bugs.

I pretty much stopped trying to make OpenMW play nicely with 3.6.x when you 
disappeared as there wasn't much point if nothing would be mergeable until 
you had more time, and now you do, I don't have much.

Anyway, on to the matter at hand, I don't get the crash, but I'm missing 
some commits in the 3.6 branch, and also I still have one of my proposed 
fixes. I'm making things more upstream-like, and I'll add another sentence 
once everything's rebuilt.

So after waiting an age for everything to rebuild, I got reminded that the 
occlusion query API got changed by Julien Valentine's recent PR. He made a 
PR for OpenMW that was supposed to resolve that, but obviously it didn't 
work until I tweaked it. Once I'd built everything, I tested it, and I'm 
not seeing the crash here. This is with a Debug build of OpenMW and OSG, 
and on Windows, and I don't think anyone else is using debug builds of 
both, especially not on Windows.

I guess that means that I've not really given any more information beyond 
this not being something that happens for everyone. It might be dependent 
on other factors, so a more detailed description of how reliable the crash 
is and whether it's dependent on anything is needed before anyone can do 
anything on OpenMW's end.

One thing of note is that the OpenMW profiler doesn't use the default font 
(at least on my machine). It uses a truetype one. I seem to remember seeing 
it use the default font in the past, and it's not impossible that this is 
toggled via a setting I've forgotten about, but I've had a good look and 
can't find one.

So that's what I know.


On Monday, 27 January 2020 09:57:23 UTC, Robert Osfield wrote:
> Hi Fiabian,
> On Monday, 27 January 2020 09:41:43 UTC, Fabian Roth wrote:
>> Hi,
>> I am currently testing this RC with openmw.
>> If i have the fps display or profiler open while exiting the application 
>> i get a crash on exit.
>> I am not sure if this is due to a bug in my build, a bug in openmw or a 
>> real issue with osg.
>> The issue seems to be related to the destruction of the default font, but 
>> i was not able to investigate further.
>> Attached is a Backtrace of the issue i am currently observing.
> That stack trace looks like the automatic clean up of the ObjectCache with 
> the DefaultFont within it is related somehow to the crash.  How the 
> DefaultFont is managed has changed, to address bugs ironically, and in a 
> general sense the clean up the stack trace looks just fine to me, it's 
> roughly what I'd expect to happen.  However, I don't have any clear idea 
> why in this instance the crash has occurred.
> Given there isn't any obvious amiss we are unfortunately are left to widen 
> out the search for what is amiss. 
> Does running an OSG example like osgtext fail?
> Do others in the OpenMMW community seen this same crash?
> Is it possible to run OpenMMW single threaded to see if there might be 
> some thread interaction?
> What OS/compile and OpenMMW version combination are you using?
> One possible cause of crash like this is memory corruption during the run 
> of the application that is only revealed on clean up.  Using a memory tools 
> like valgrind might be spot this type of issue.
> Perhaps others might have seen something similar and can help shed some 
> light on the nature of the crash.
> If it's possible to recreate the crash with an standard OSG example, or a 
> small modification of one, then this would be really helpful for me to jump 
> in a start investigating the issue.
> Cheers.
> Robert.

You received this message because you are subscribed to the Google Groups "OpenSceneGraph Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osg-users+unsubscribe at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osg-users/ff578130-867c-4c93-9fb0-fd573b20ab91%40googlegroups.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20200127/b7673768/attachment.html>

More information about the osg-users mailing list