[openvrml-develop] Crash-on-exit versus API change

[Braden M. <br...@en...>]

I've got a fix for bug 1530554[1] nearly ready to commit.  This one was
particularly annoying to me since it produced random failures in "make
check".

The bad news is that the fix required an API change. That means the fix
won't appear in a release until 0.17.0.

I have quite a few irons in the fire; but right now, the trunk doesn't
have much in the way of functional changes. Per my previous postings on
the topic, I've been planning to hold 0.17 until the modularization work
is done--and that's still some months away. However, if fixing this
crash is important enough that a release be made with the fix ASAP, the
modularization stuff can wait for 0.18.

Applications are only likely to hit this bug if the browser gets
destroyed in the middle of fetching a resource. So, if anyone's hit
this, or thinks they could do so easily, please speak up.

[1] http://sourceforge.net/tracker/index.php?func=detail&aid=1530554&group_id=7151&atid=107151

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>