2006/7/4, Robert Osfield <[EMAIL PROTECTED]>:
i tried to compile it, and i got similar trouble Observer class
i am not running in single threaded, so i have to lock / unlock some shared resources. At the moment
may application just using the OpenThreads stuff. Mutex, Thread only this both classes.
the code above should show where i have an issue (only) on one machine. because normally i use
mutex.lock to lock a mutex, as common way. but if i implement my own lock :
while ( ! mutex.tryLock() ) SwitchToThread();
instead of mutex.lock() the issue will more or less disappear.
but i have to retry and debug it. i hope i will find out what would be the issue.
adegli
Hi Adrian,
On 7/3/06, Adrian Egli <[EMAIL PROTECTED]> wrote:
> i didn't yet rebuild every thing with vc6. but the first part of the
> osg.lib source has compiled as well as it did before. i will rebuild
> everythings once this week over night. at the moment i
> has to work on the computer installed vc6.
Let me know how things progress, it'll be good to know where we stand w.r.t 1.1.
i tried to compile it, and i got similar trouble Observer class
> by the way: the big performance issue i have on the dual core machine with
> latest windows xp version, is NOT disappered with the latest CVS version. i
> work on this issue further. the trouble appears on sleep -> the command want
> switch the thread. (its a guess i have because i can reduce the effect by
> replacing mutex.lock with while ( ! mutex.tryLock() ) SwitchToThread(); it's
> bad but may i will find out the troubles i have. i tested it with a compiled
> vc2003, vc2005 and also with vc6, it's not a copiler issue it seems to be
> deeper in the windows library kernel32.dll or something near there.
If you are running your app single threaded then you shouldn't need to
mutex osg::Referenced::ref()/unref(), it'd be worth checking on this.
Your above code references look specific to your app though, so I'm
not sure there is much on the OSG side that can be done to help.
i am not running in single threaded, so i have to lock / unlock some shared resources. At the moment
may application just using the OpenThreads stuff. Mutex, Thread only this both classes.
the code above should show where i have an issue (only) on one machine. because normally i use
mutex.lock to lock a mutex, as common way. but if i implement my own lock :
while ( ! mutex.tryLock() ) SwitchToThread();
instead of mutex.lock() the issue will more or less disappear.
but i have to retry and debug it. i hope i will find out what would be the issue.
adegli
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
