Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread Jean-Sébastien Guay

Hi Robert,


This very much looks like a driver bug so we'll need to contact NVidia
and get them on to.  Anyone with a hotline to NVidia?


The driver devs I met at Siggraph said that sending to

[EMAIL PROTECTED]

was our best bet when we found bugs in their OpenGL implementations. 
They also added that including a simple example (OpenGL only of course) 
that reproduces the bug helps a lot (of course).


Wojtek also had some contact with NVidia devs for the double-makecurrent 
bug, and apparently got some response from them, so perhaps he can advise.


J-S
--
__
Jean-Sebastien Guay[EMAIL PROTECTED]
   http://www.cm-labs.com/
http://whitestar02.webhop.org/
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread Wojciech Lewandowski
Hi, I wish I had some friends at NVidia. But unfortunately they not seem to
treat me specially. I went through standard Bug report form on developer
NVidia website. At least last time they let me know they repeated the bug
and did something about it. 2 former cases when I sent reports were ignored.
But former cases were not accompanied by the source code. So if I was to
suggest something it would be creation of OpenGL repro and uploading this
example along on the bug report form. I believe last time I added
OpenSceneGraph to the list of projects requiring fixes. So you may add this
bug under this project.

Cheers,
Wojtek

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Jean-Sebastien Guay
Sent: Tuesday, November 11, 2008 3:41 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Many RTT cameras, strange out of memory errors on
Linux


Hi Robert,

 This very much looks like a driver bug so we'll need to contact NVidia
 and get them on to.  Anyone with a hotline to NVidia?

The driver devs I met at Siggraph said that sending to

[EMAIL PROTECTED]

was our best bet when we found bugs in their OpenGL implementations.
They also added that including a simple example (OpenGL only of course)
that reproduces the bug helps a lot (of course).

Wojtek also had some contact with NVidia devs for the double-makecurrent
bug, and apparently got some response from them, so perhaps he can advise.

J-S
--
__
Jean-Sebastien Guay[EMAIL PROTECTED]
http://www.cm-labs.com/
 http://whitestar02.webhop.org/
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread J.P. Delport

Hi Robert,

thanks for looking into this.

Just ran it on Core2 Duo 2GB machine, GeForce 8800GT 256MB driver 
177.67, Debian Sid.


I had to add a bit more fbo's before a crash, but maybe it's cos the 
machine is slower.


With some smaller (32x32) sizes I even managed a X crash and restart.

osgmemorytest --window --fbo 512 512 -g 300
iteration 0
Got an X11ErrorHandling call display=0x80c3418 event=0xbfe574d0
BadAlloc (insufficient resources for operation)
Major opcode: 143
Minor opcode: 27
Error code: 11
Request serial: 2848
Current serial: 2849
  ResourceID: 48234499
Got an X11ErrorHandling call display=0x80c3418 event=0xbfe57530
BadDrawable (invalid Pixmap or Window parameter)
Major opcode: 145
Minor opcode: 4
Error code: 9
Request serial: 2849
Current serial: 2849
  ResourceID: 48234499
Warning: detected OpenGL error 'out of memory' after applying attribute 
FrameBufferObject 0x80aa470


jp

Robert Osfield wrote:

Hi Guys,

I've now got an osgmemorytest example checked into svn/trunk, it
currently supports allocating windows, pbuffers and textures/fbo for
each of the windows/pbuffers created.   I get some wierd results...

The follow test run:

   osgmemorytest --window --fbo 1024 1024 -g 150

Succeeds.  While using a smaller fbo it fails at the 145'th fbo:

osgmemorytest --window --fbo 512 512 -g 150

With the command line output:

iteration 0
Got an X11ErrorHandling call display=0x653c50 event=0x7fff31e452c0
BadAlloc (insufficient resources for operation)
Major opcode: 128
Minor opcode: 27
Error code: 11
Request serial: 1071
Current serial: 1072
  ResourceID: 27262979
Got an X11ErrorHandling call display=0x653c50 event=0x7fff31e452c0
BadWindow (invalid Window parameter)
Major opcode: 145
Minor opcode: 4
Error code: 3
Request serial: 1072
Current serial: 1072
  ResourceID: 27262979
Warning: detected OpenGL error 'out of memory' after applying
attribute FrameBufferObject 0x6513c0

Exception caught, contexts completed = 0, gl objects successfully
applied =145, error = OpenGL error

So I get an out of memory error when I use smaller FBO's. I've tried
smaller sizes like 128x128 and also get the exactly same error.  When
I run multiple contexts I get the error when the exactly the same
total number of small FBO's are allocated.  By using -c 2 to set the
number of contexts to allocate to 2, and -g 100 to limit the number of
GL objects (FBO's in this instance) to 100 per context I get the
result:

osgmemorytest --window --fbo 512 512 -g 100 -c 2
iteration 0
iteration 1
Got an X11ErrorHandling call display=0x990bd0 event=0x7fff3824f6b0
BadAlloc (insufficient resources for operation)
Major opcode: 128
Minor opcode: 27
Error code: 11
Request serial: 363
Current serial: 364
  ResourceID: 54525955
Got an X11ErrorHandling call display=0x990bd0 event=0x7fff3824f6b0
BadWindow (invalid Window parameter)
Major opcode: 145
Minor opcode: 4
Error code: 3
Request serial: 364
Current serial: 364
  ResourceID: 54525955
Warning: detected OpenGL error 'out of memory' after applying
attribute FrameBufferObject 0x625180

Exception caught, contexts completed = 1, gl objects successfully
applied =145, error = OpenGL error


The lines iteration 0 and iteration 1, show that the first context was
created with all 100 FBO's just fine. Even stranger when I up the fbo
size to 1024x1024 it's able to allocate 156 FBO's, and when higher
still it gets even further to the point of exhausting all memory on
the machine and grinding it to nearly to a halt due to pushing swap
space too hard.

All these tests are being run single threaded on my Kubuntu 7.10,
Geforce 8800GTS 640Mb, 4GB machine. From glxinfo: OpenGL version
string: 2.1.1 NVIDIA 100.14.19.

So what does this all point to?  My best guess is that the driver is
multi-threaded and if we allocate smaller FBO's they get created more
quickly and hit a threading issue in the driver.  It's pretty clearly
a driver bug.  I'm currently compiling on one of my other machines
with Kubuntu 8.10 installed.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread Robert Osfield
Hi Guys,

I've now got an osgmemorytest example checked into svn/trunk, it
currently supports allocating windows, pbuffers and textures/fbo for
each of the windows/pbuffers created.   I get some wierd results...

The follow test run:

   osgmemorytest --window --fbo 1024 1024 -g 150

Succeeds.  While using a smaller fbo it fails at the 145'th fbo:

osgmemorytest --window --fbo 512 512 -g 150

With the command line output:

iteration 0
Got an X11ErrorHandling call display=0x653c50 event=0x7fff31e452c0
BadAlloc (insufficient resources for operation)
Major opcode: 128
Minor opcode: 27
Error code: 11
Request serial: 1071
Current serial: 1072
  ResourceID: 27262979
Got an X11ErrorHandling call display=0x653c50 event=0x7fff31e452c0
BadWindow (invalid Window parameter)
Major opcode: 145
Minor opcode: 4
Error code: 3
Request serial: 1072
Current serial: 1072
  ResourceID: 27262979
Warning: detected OpenGL error 'out of memory' after applying
attribute FrameBufferObject 0x6513c0

Exception caught, contexts completed = 0, gl objects successfully
applied =145, error = OpenGL error

So I get an out of memory error when I use smaller FBO's. I've tried
smaller sizes like 128x128 and also get the exactly same error.  When
I run multiple contexts I get the error when the exactly the same
total number of small FBO's are allocated.  By using -c 2 to set the
number of contexts to allocate to 2, and -g 100 to limit the number of
GL objects (FBO's in this instance) to 100 per context I get the
result:

osgmemorytest --window --fbo 512 512 -g 100 -c 2
iteration 0
iteration 1
Got an X11ErrorHandling call display=0x990bd0 event=0x7fff3824f6b0
BadAlloc (insufficient resources for operation)
Major opcode: 128
Minor opcode: 27
Error code: 11
Request serial: 363
Current serial: 364
  ResourceID: 54525955
Got an X11ErrorHandling call display=0x990bd0 event=0x7fff3824f6b0
BadWindow (invalid Window parameter)
Major opcode: 145
Minor opcode: 4
Error code: 3
Request serial: 364
Current serial: 364
  ResourceID: 54525955
Warning: detected OpenGL error 'out of memory' after applying
attribute FrameBufferObject 0x625180

Exception caught, contexts completed = 1, gl objects successfully
applied =145, error = OpenGL error


The lines iteration 0 and iteration 1, show that the first context was
created with all 100 FBO's just fine. Even stranger when I up the fbo
size to 1024x1024 it's able to allocate 156 FBO's, and when higher
still it gets even further to the point of exhausting all memory on
the machine and grinding it to nearly to a halt due to pushing swap
space too hard.

All these tests are being run single threaded on my Kubuntu 7.10,
Geforce 8800GTS 640Mb, 4GB machine. From glxinfo: OpenGL version
string: 2.1.1 NVIDIA 100.14.19.

So what does this all point to?  My best guess is that the driver is
multi-threaded and if we allocate smaller FBO's they get created more
quickly and hit a threading issue in the driver.  It's pretty clearly
a driver bug.  I'm currently compiling on one of my other machines
with Kubuntu 8.10 installed.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread Robert Osfield
Hi JP et al.

On Tue, Nov 11, 2008 at 2:21 PM, Robert Osfield
[EMAIL PROTECTED] wrote:
 I'm going to add an optional sleep into the each gl object apply to
 see if this make any difference.

I've added an osgmemorytest command line option --delay microseconds
that invokes an OpenThread::Thread::microSleep(microsecons) before
each OpenGL object apply.

I've tried a range of sleeps and none have any effect on the number of
FBO's that the driver is able to create.  So this discounts the theory
that we're push OpenGL fifo so quickly that it's invoke threading
issues.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-11 Thread Robert Osfield
Hi JP,

I've got some odd X server crashes and restart as well.  On my little
shuttle with Kubuntu 8.10 on it it gets to 215 fbo's at 512x512.  This
is with a  lowe end128Mb Geforce 7 card + only 1Gb memory rather 4GB
on my main machine.  The Kubuntu 8.10 machine has OpenGL version
string 2.1.2 NVIDIA 177.80.  So it looks like later drivers, or
perhaps just slower machines are better off w.r.t the memory errors.

I'm going to add an optional sleep into the each gl object apply to
see if this make any difference.

This very much looks like a driver bug so we'll need to contact NVidia
and get them on to.  Anyone with a hotline to NVidia?

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-10 Thread J.P. Delport

Hi,

Robert Osfield wrote:

Hi J.P,

On Mon, Nov 10, 2008 at 6:56 AM, J.P. Delport [EMAIL PROTECTED] wrote:

if anyone has some spare time, please execute the attached test app under
Linux. I am still unsure if our problems are related to NVidia driver, Linux
distribution, ...


I haven't had a chance to test but I will this test it this week.  In
fact I will be writing a general memory test program that will
allocate till exhaustion on a range of OSG classes that manage OpenGL,
FBO's will be among the tests.  I've had feedback that of poorer
scaling in OSG/OpenGL memory under Vista (an 8GB machine) than I'm
getting under 4GB linux box, so my guess is that we may well find
different OpenGL/OSG features scaling well on some
OS's/drivers/hardware and poorly on others, each with their own
oddities...


This would be very informative, thanks Robert. I'm still unsure whether 
 our problem is related to FBOs/Cameras+Renderstage.


regards
jp



Robert.


--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-10 Thread Alberto Luaces
Hi JP,

I always get the same errors (92  80) during execution (see below). My system 
is

Linux 2.6.26-1-amd64
GeForce 7600 GS, driver 173.14.12
256 MB

Got an X11ErrorHandling call display=0x114f600 event=0x7fff4f229750
BadWindow (invalid Window parameter)
Major opcode: 92
Minor opcode: 4
Error code: 3
Request serial: 3a86
Current serial: 3a86
  ResourceID: 2e3
Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5
Got an X11ErrorHandling call display=0x114f600 event=0x7fff4f2296e0
BadAlloc (insufficient resources for operation)
Major opcode: 80
Minor opcode: 1b
Error code: b
Request serial: 3a87
Current serial: 3a88
ResourceID: 2e3


El Lunes 10 Noviembre 2008ES 07:56:25 J.P. Delport escribió:
 Hi all,

 if anyone has some spare time, please execute the attached test app
 under Linux. I am still unsure if our problems are related to NVidia
 driver, Linux distribution, ...

 thanks
 jp

 J.P. Delport wrote:
  Hi all,
 
  a colleague of mine is trying to implement an image processing algorithm
  that requires many RTT cameras (+-150).
 
  His algorithm runs on his Windows machine, but fails under Linux (I'm
  quite sad about it :) with some of the following errors:
 
  --8--
 
  Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
  BadAlloc (insufficient resources for operation)
 
  Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
  BadDrawable (invalid Pixmap or Window parameter)
 
  Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
  RenderStage::drawInner(,) FBO status= 0x8cd5
 
  --8--
 
  We've narrowed the problem down to just camera creation and frame
  rendering. Texture sizes do not seem to influence the error. I've made a
  small test application (attached) that creates the errors.
 
  On my Linux laptop the errors start appearing at around 220 cameras. On
  another Linux machine we can get about 10 more. On Windows we've been
  able to test up to 3000 (the apps starts up too slowly if we add more).
 
  Does anyone have any ideas about why and where the cameras are creating
  X resources?
 
  Art (if you are around), does osgPPU use osg::Camera? Maybe we can move
  to osgPPU if not.
 
  Any pointers to help us debug are welcome.
 
  regards
  jp
 
 
 
  
 
  ___
  osg-users mailing list
  osg-users@lists.openscenegraph.org
  http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-10 Thread Robert Osfield
Hi J.P,

On Mon, Nov 10, 2008 at 6:56 AM, J.P. Delport [EMAIL PROTECTED] wrote:
 if anyone has some spare time, please execute the attached test app under
 Linux. I am still unsure if our problems are related to NVidia driver, Linux
 distribution, ...

I haven't had a chance to test but I will this test it this week.  In
fact I will be writing a general memory test program that will
allocate till exhaustion on a range of OSG classes that manage OpenGL,
FBO's will be among the tests.  I've had feedback that of poorer
scaling in OSG/OpenGL memory under Vista (an 8GB machine) than I'm
getting under 4GB linux box, so my guess is that we may well find
different OpenGL/OSG features scaling well on some
OS's/drivers/hardware and poorly on others, each with their own
oddities...

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-10 Thread J.P. Delport

Hi Alberto,

thanks for the testing, it does seem that the problem is more general 
than my specific Linux setup.


jp

Alberto Luaces wrote:

Hi JP,

I always get the same errors (92  80) during execution (see below). My system 
is


Linux 2.6.26-1-amd64
GeForce 7600 GS, driver 173.14.12
256 MB

Got an X11ErrorHandling call display=0x114f600 event=0x7fff4f229750
BadWindow (invalid Window parameter)
Major opcode: 92
Minor opcode: 4
Error code: 3
Request serial: 3a86
Current serial: 3a86
  ResourceID: 2e3
Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5
Got an X11ErrorHandling call display=0x114f600 event=0x7fff4f2296e0
BadAlloc (insufficient resources for operation)
Major opcode: 80
Minor opcode: 1b
Error code: b
Request serial: 3a87
Current serial: 3a88
ResourceID: 2e3


El Lunes 10 Noviembre 2008ES 07:56:25 J.P. Delport escribió:

Hi all,

if anyone has some spare time, please execute the attached test app
under Linux. I am still unsure if our problems are related to NVidia
driver, Linux distribution, ...

thanks
jp

J.P. Delport wrote:

Hi all,

a colleague of mine is trying to implement an image processing algorithm
that requires many RTT cameras (+-150).

His algorithm runs on his Windows machine, but fails under Linux (I'm
quite sad about it :) with some of the following errors:

--8--

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
BadAlloc (insufficient resources for operation)

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
BadDrawable (invalid Pixmap or Window parameter)

Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5

--8--

We've narrowed the problem down to just camera creation and frame
rendering. Texture sizes do not seem to influence the error. I've made a
small test application (attached) that creates the errors.

On my Linux laptop the errors start appearing at around 220 cameras. On
another Linux machine we can get about 10 more. On Windows we've been
able to test up to 3000 (the apps starts up too slowly if we add more).

Does anyone have any ideas about why and where the cameras are creating
X resources?

Art (if you are around), does osgPPU use osg::Camera? Maybe we can move
to osgPPU if not.

Any pointers to help us debug are welcome.

regards
jp





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-09 Thread J.P. Delport

Hi all,

if anyone has some spare time, please execute the attached test app 
under Linux. I am still unsure if our problems are related to NVidia 
driver, Linux distribution, ...


thanks
jp

J.P. Delport wrote:

Hi all,

a colleague of mine is trying to implement an image processing algorithm 
that requires many RTT cameras (+-150).


His algorithm runs on his Windows machine, but fails under Linux (I'm 
quite sad about it :) with some of the following errors:


--8--

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
BadAlloc (insufficient resources for operation)

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
BadDrawable (invalid Pixmap or Window parameter)

Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5

--8--

We've narrowed the problem down to just camera creation and frame 
rendering. Texture sizes do not seem to influence the error. I've made a 
small test application (attached) that creates the errors.


On my Linux laptop the errors start appearing at around 220 cameras. On 
another Linux machine we can get about 10 more. On Windows we've been 
able to test up to 3000 (the apps starts up too slowly if we add more).


Does anyone have any ideas about why and where the cameras are creating 
X resources?


Art (if you are around), does osgPPU use osg::Camera? Maybe we can move 
to osgPPU if not.


Any pointers to help us debug are welcome.

regards
jp





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-07 Thread J.P. Delport

Hi,

yes, it uses FBO, I confirmed using DEBUG notify level. That is part of 
the reason why I'm stumped by the X errors.


Hardware supports FBO, we are running lots of other FBO algo's requiring 
512MB memory without problems.


jp

Robert Osfield wrote:

Hi J.P,

I haven't tried the example yet, but if the camera is allocating X11
resources it sounds like its using a pbuffer rather than an FBO.  Are
you using FBOs?  Does you hardware/drivers support FBO?

Robert.

On Fri, Nov 7, 2008 at 12:40 PM, J.P. Delport [EMAIL PROTECTED] wrote:

Hi all,

a colleague of mine is trying to implement an image processing algorithm
that requires many RTT cameras (+-150).

His algorithm runs on his Windows machine, but fails under Linux (I'm quite
sad about it :) with some of the following errors:

--8--

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
BadAlloc (insufficient resources for operation)

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
BadDrawable (invalid Pixmap or Window parameter)

Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5

--8--

We've narrowed the problem down to just camera creation and frame rendering.
Texture sizes do not seem to influence the error. I've made a small test
application (attached) that creates the errors.

On my Linux laptop the errors start appearing at around 220 cameras. On
another Linux machine we can get about 10 more. On Windows we've been able
to test up to 3000 (the apps starts up too slowly if we add more).

Does anyone have any ideas about why and where the cameras are creating X
resources?

Art (if you are around), does osgPPU use osg::Camera? Maybe we can move to
osgPPU if not.

Any pointers to help us debug are welcome.

regards
jp


--
This message is subject to the CSIR's copyright terms and conditions, e-mail
legal notice, and implemented Open Document Format (ODF) standard. The full
disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.  MailScanner thanks Transtec
Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-07 Thread Art Tevs
Hi J.P.,

Thats a really strange behaviour. Could it be that you ran into driver issues. 
I mean maybe linux gpu drivers doesn't work well with so much fbo's hanging 
around.

osgPPU doesn't use cameras. It require a camera attachment only to get the 
output (RTT) texture out of the camera. However in the current version even 
that is not required, because you can just provide the pipeline with any 
texture by UnitTexture class. Hence if you ahve a texture or many textures, you 
can use osgPPU to run the computations on it.

Best regards,
art

 
 
 Art (if you are around), does osgPPU use osg::Camera? Maybe
 we can move to osgPPU if not.
 
 Any pointers to help us debug are welcome.
 
 regards
 jp
 
 
 -- This message is subject to the CSIR's copyright
 terms and conditions, e-mail legal notice, and implemented
 Open Document Format (ODF) standard. The full disclaimer
 details can be found at
 http://www.csir.co.za/disclaimer.html.
 
 This message has been scanned for viruses and dangerous
 content by MailScanner, and is believed to be clean. 
 MailScanner thanks Transtec Computers for their support.
 
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


  
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-07 Thread Robert Osfield
Hi J.P,

I haven't tried the example yet, but if the camera is allocating X11
resources it sounds like its using a pbuffer rather than an FBO.  Are
you using FBOs?  Does you hardware/drivers support FBO?

Robert.

On Fri, Nov 7, 2008 at 12:40 PM, J.P. Delport [EMAIL PROTECTED] wrote:
 Hi all,

 a colleague of mine is trying to implement an image processing algorithm
 that requires many RTT cameras (+-150).

 His algorithm runs on his Windows machine, but fails under Linux (I'm quite
 sad about it :) with some of the following errors:

 --8--

 Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
 BadAlloc (insufficient resources for operation)

 Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
 BadDrawable (invalid Pixmap or Window parameter)

 Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
 RenderStage::drawInner(,) FBO status= 0x8cd5

 --8--

 We've narrowed the problem down to just camera creation and frame rendering.
 Texture sizes do not seem to influence the error. I've made a small test
 application (attached) that creates the errors.

 On my Linux laptop the errors start appearing at around 220 cameras. On
 another Linux machine we can get about 10 more. On Windows we've been able
 to test up to 3000 (the apps starts up too slowly if we add more).

 Does anyone have any ideas about why and where the cameras are creating X
 resources?

 Art (if you are around), does osgPPU use osg::Camera? Maybe we can move to
 osgPPU if not.

 Any pointers to help us debug are welcome.

 regards
 jp


 --
 This message is subject to the CSIR's copyright terms and conditions, e-mail
 legal notice, and implemented Open Document Format (ODF) standard. The full
 disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

 This message has been scanned for viruses and dangerous content by
 MailScanner, and is believed to be clean.  MailScanner thanks Transtec
 Computers for their support.


 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


[osg-users] Many RTT cameras, strange out of memory errors on Linux

2008-11-07 Thread J.P. Delport

Hi all,

a colleague of mine is trying to implement an image processing algorithm 
that requires many RTT cameras (+-150).


His algorithm runs on his Windows machine, but fails under Linux (I'm 
quite sad about it :) with some of the following errors:


--8--

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991100
BadAlloc (insufficient resources for operation)

Got an X11ErrorHandling call display=0x80a8c80 event=0xbf991160
BadDrawable (invalid Pixmap or Window parameter)

Warning: detected OpenGL error 'out of memory' after RenderBin::draw(,)
RenderStage::drawInner(,) FBO status= 0x8cd5

--8--

We've narrowed the problem down to just camera creation and frame 
rendering. Texture sizes do not seem to influence the error. I've made a 
small test application (attached) that creates the errors.


On my Linux laptop the errors start appearing at around 220 cameras. On 
another Linux machine we can get about 10 more. On Windows we've been 
able to test up to 3000 (the apps starts up too slowly if we add more).


Does anyone have any ideas about why and where the cameras are creating 
X resources?


Art (if you are around), does osgPPU use osg::Camera? Maybe we can move 
to osgPPU if not.


Any pointers to help us debug are welcome.

regards
jp


--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.




osg_many_cams.tgz
Description: application/compressed-tar
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org