Note:

I asked Filip to post to this list, since I suspect that this is an X
server-related bug and not due to an issue with VirtualGL (although
VirtualGL obviously exposes it.)  I haven't been able to repro the issue
using a simple test program.  The application is basically failing on
the XCreatePixmap() call within VirtualGL's implementation of
glXUseXFont().  The implementation of that function in VirtualGL is
borrowed from Mesa.  I could understand a failure in TightVNC, since
there were a lot of issues with that code that have been fixed in
TurboVNC.  Not the least among these issues was that TightVNC's Xvnc
implementation used the stack for allocating Pixmaps and XImages,
whereas TurboVNC uses the heap.  That would explain this, except that
I'm pretty sure TigerVNC uses the heap as well.

Filip, I happened to think that perhaps what we need to figure out is
what arguments are being passed to XCreatePixmap(), which may allow for
writing a test program that repros this outside of the app.  If you'll
tell me what O/S you're using, I'll send you a custom build of VirtualGL
that has additional tracing information.


On 12/8/11 6:47 AM, filip.ged...@gridcore.se wrote:
> I am trying to run an application called Oasys Primer remotely using
> TigerVNC and VirtualGL.
> The application starts and the process is reading event data from the X
> socket. The problem is that the ui is not updating and not responding to
> any user input.
> 
> Enabling VGL_TRACE shows that a call to glXUseXFont seems to fail.
> Here is an excerpt from the console when running the application:
>   [VGL] glXUseXFont (font=0x00a00277 first=0 count=256 list_base=3073 )
> 9.381056 ms
>   [VGL] glXUseXFont (font=0x00a00278 first=0 count=256 list_base=3329 )
> 11.617899 ms
>   [VGL] glXUseXFont (font=0x00a00279 first=0 count=256 list_base=3585
> Space allocation failure (BadAlloc) when allocating Pixmap
>   Trying XSync.
>   [VGL] dlopen
> (filename=/usr/X11R6/lib/X11/locale/lib64/common/xlcDef.so.2 flag=1
> retval=0x0548b4a0)
>   X Server error detected:
>     BadDrawable (invalid Pixmap or Window parameter)
>    Protocol request: 55
>    Resource ID:      a00299
> 
> No further VGL calls are printed beyond this point.
> 
> I have tried a number of different X servers, all except TurboVNC gives
> the same error when using VGL. If I run without VGL the application
> works as expected when using the X servers mesa implementation where
> available.
> 
> The versions tested are:
> TightVNC 1.2.9
> TigerVNC 1.1.0, 1.1.80 (DRC pre release build)
> TurboVNC 1.0.2
> Xorg 6.9.0
> VGL 2.2.1, 2.3 beta
> 
> Anyone that have experience running this application or have experienced
> similar problems?
> 
> --
> Filip Gedell
> 
> 
> ------------------------------------------------------------------------------
> Cloud Services Checklist: Pricing and Packaging Optimization
> This white paper is intended to serve as a reference, checklist and point of 
> discussion for anyone considering optimizing the pricing and packaging model 
> of a cloud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> 
> 
> 
> _______________________________________________
> Tigervnc-users mailing list
> Tigervnc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tigervnc-users

------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users

Reply via email to