CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   ParaView (https://www.cfd-online.com/Forums/paraview/)
-   -   [OpenFOAM] ParaFoam BadLength error (https://www.cfd-online.com/Forums/paraview/61069-parafoam-badlength-error.html)

coops May 10, 2007 00:37

ParaFoam BadLength error
 
Hello all,

I have installed OF1.4 and I have run some of the tutorial cases. I then used paraFoam to view thw results but when I try to create and animation or save a figure paraFoam closes and reports:

paraFoam . shockTube
/*---------------------------------------------------------------------------*\
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: 1.4 |
| \ / A nd | Web: http://www.openfoam.org |
| \/ M anipulation | |
\*---------------------------------------------------------------------------*/

X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 28 ()
Serial number of failed request: 26816
Current serial number in output stream: 26818

Has anyone else experienced this? Any idea how this problem can be fixed.

Thanks,

Shaun

coops May 13, 2007 01:54

No one else faced this problem
 
No one else faced this problem?

7islands May 13, 2007 04:16

Hi, I also get similar errors
 
Hi,
I also get similar errors under openSUSE 10.2 x86_64 but no idea as to fix anyway http://www.cfd-online.com/OpenFOAM_D...lipart/sad.gif

Takuya

paraFoam sonicFoam shockTube
/*---------------------------------------------------------------------------*\
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: 1.4 |
| \ / A nd | Web: http://www.openfoam.org |
| \/ M anipulation | |
\*---------------------------------------------------------------------------*/

...
File ->"Save Animiation" or "Save View Image"
...


X Error of failed request: GLXBadContext
Major opcode of failed request: 130 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 23940
Current serial number in output stream: 23940

alberto May 13, 2007 10:35

Hello. Paraview works OK for m
 
Hello. Paraview works OK for me. It seems a problem with your OpenGL libraries.

Are you using accelerated drivers for your video card?

Regards,
A.

7islands May 13, 2007 19:50

Hi, Thanks, it's so encouragi
 
Hi,
Thanks, it's so encouraging to know saving images works at least in a case.
I have to stick with the open-source driver to use a dual-head merged framebuffer setup with my old Radeon 9200 video (the merged framebuffer of the vendor-supplied driver doesn't work). The rendering itself works fine but just saving images makes paraFoam crash.
Maybe I should consider replacing the video card...

Takuya

coops May 14, 2007 02:35

Hi, I had used openFaom 1.3
 
Hi,

I had used openFaom 1.3 with no problems, I was able to create and save animations and also images, but since I upgraded to OpenFoam 1.4 I haven't been able to save the images and animations. I will need to look into the OpenGL libraries but it did work with the older version!

Shaun

alberto May 14, 2007 03:51

FLUENT have similar issues wit
 
FLUENT have similar issues with some nVidia cards, if you don't have installed the accelerated nVidia drivers.

If this is the case, your you find a tutorial to install them using RPM's provided by Novell: http://en.opensuse.org/NVIDIA

Regards,
A.

msrinath80 June 15, 2007 21:07

Greetings everyone! My Lapt
 
Greetings everyone!

My Laptop has an Intel GMA chipset (onboard graphics). I think I have found a workaround to this IRRITATING GLXBadContext error. Based on my google search, I tried one of the suggestions from the freedesktop.org thread[1] and it solved my problem instantly. There is no need to recompile paraview and/or parafoam by commenting out the two offscreen rendering lines as discussed elsewhere[2].

The proposed workaround is to add the following line to the 'ServerLayout' section in your /etc/xorg.conf. Please make sure to create a backup before you modify it.

For Example:

Section "ServerLayout"
Option "AIGLX" "false"
EndSection

FYI: The other way to work around this problem is to disable OpenGL acceleration by using the software cursor [Not recommended!].

[1] https://bugs.freedesktop.org/show_bug.cgi?id=9200
[2] http://public.kitware.com/pipermail/...st/086674.html

msrinath80 June 15, 2007 21:09

Correction: The file location
 
Correction: The file location is /etc/X11/xorg.conf.

7islands June 17, 2007 01:04

It worked! Thanks!! T.
 
It worked! Thanks!!

T.

musahossein June 21, 2008 16:57

when I open paraFoam as follow
 
when I open paraFoam as follows and accept the cavity.foam case to be uploaded, I get the following messages:

musa@linux:~> paraFoam $FOAM_RUN/tutorials/icoFoam cavity


--> FOAM FATAL IO ERROR : attempt to read beyond EOF

file: /home/musa/OpenFOAM/musa-1.4.1/run/tutorials/icoFoam/cavity/0/U::internalField at line 30.

From function ITstream::read(token& t)
in file db/IOstreams/Tstreams/ITread.C at line 70.

FOAM exiting

Any sugestions as to how to solve this problem? Thanks

danj July 13, 2008 02:31

I have the same problem as you
 
I have the same problem as you musaddeque, if anyone can find a solution it would be much appreciated.

Dan.

walter_balbert January 22, 2009 19:10

I have the same Problem gettin
 
I have the same Problem getting the GLXBadContext error.
I'm using OpenFoam1.5

Anyone knows where can I find the /etc/xorg.conf.
file to fix the problem as pUI described?

Walter

walter_balbert January 22, 2009 19:19

I have the same Problem gettin
 
I have the same Problem getting the GLXBadContext error.
I'm using OpenFoam1.5

Anyone knows where can I find the /etc/xorg.conf.
file to fix the problem as pUI described?

Walter

walter_balbert January 23, 2009 11:20

Found the folder an it worked!
 
Found the folder an it worked!

Thanks a lot.
W.


All times are GMT -4. The time now is 21:58.