More generally I'm not convinced that we need to deprecate the none
ref versions. I'd be inclined towards just documenting that
multi-threaded reads should use the Ref versions.
It might not be convincing to have to go back to the code base and remove these
unsafe sections of code, but
Hi Ryan,
On Wed, Dec 16, 2009 at 9:43 AM, Ryan H. Kawicki
ryan.h.kawi...@boeing.com wrote:
It might not be convincing to have to go back to the code base and remove
these unsafe sections of code, but by having a set of documentation is really
not going to help eighty or ninety percent of the
Robert,
I just wanted to respond with my investigations and observations.
I sounds like the lack of a readRefFontFile() is a potential problem.
In the case of include/osgDB/ReadFile there are readRefNodeFile() etc.
functions that pass back a ref_ptr rather than a C pointer, and are
all
Hi Ryan,
On Mon, Dec 14, 2009 at 10:38 AM, Ryan H. Kawicki
ryan.h.kawi...@boeing.com wrote:
Observation 1:
Using the unsafe versions is bad. Now we know and knowing is half the
battler, but should this be take further. It might be a good idea to tag the
unsafe versions as deprecated, this
I've been investigating a crash that has plagued us for quite some time. I've
finally gotten some time to sit down and take a look at this.
Details:
OSG: 2.8.1
OS: WinXP SP3 32Bit
CPU: 8 Core 2.5GHz Xenon
Graphics: Quadro FX 3700 512 MB
Memory: Plenty
Description:
Our application embeds OSG
Hi Ryan,
I sounds like the lack of a readRefFontFile() is a potential problem.
In the case of include/osgDB/ReadFile there are readRefNodeFile() etc.
functions that pass back a ref_ptr rather than a C pointer, and are
all safer in multi-thread situations where object cache is in play.
Could you
6 matches
Mail list logo