[Paraview-developers] xdisplay-test + display=1 => segfault

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Wed May 10 13:24:56 EDT 2017


Jens,

Can you try closing current render view and creating new view? Does
that fail even when you pass `--disable-xdisplay-test`? In my
experience, whenever I have seen a crash in pvserver startup which can
be circumvented by `--disable-xdisplay-test`, it's been a driver bug
with creating multiple opengl contexts.

Utkarsh

On Wed, May 10, 2017 at 11:51 AM, "Göbbert, Jens Henrik"
<j.goebbert at fz-juelich.de> wrote:
> Hello ParaView-Team,
>
> we recently have experienced reproducible a segfaults of Xorg on display=1
> (on CentOS 7.2 server with two NVIDIA Tesla K40), when used with:
> --server--
>   parallel ParaView/5.3.0 session (compiled with VTK_USE_X)
>   over turboVNC(2.1.1) +VirtualGL(2.2.1)
> --client--
>   from a Windows7 client
>   with turboVNC(2.1.1)
> (other versions of turboVNC and VirtualGL led to the same
>
> This crash does _NOT_ happen, if the vncviewer(yes: vncVIEWER!) is running
> on a Linux machine.
> As soon as ParaView GUI (running on the server with turboVNC+VirtualGL, too)
> connects to the pvservers running on the same machine, at least one of the
> pvservers on display=1 crashes (MPI leads then to a stop of the other
> pvservers).
> The crash of the pvserver on display 1 leads to a crash of Xorg of display 1
> - or it is the other way round.
>
> We found that this crash can be avoided by starting the pvservers with the
> flag "--disable-xdisplay-test"
> I report this here, as it took some time to stumble over the flag
> "--disable-xdisplay-test" and this mail might help someone else.
> It seems as if the xdisplay-test is doing some nasty stuff ...
>
> As this bug is related to the OS(=Windows) of the client running turboVNC
> the xdisplay-test might trigger a bug in turboVNC or Xorg itself...
>
> Best,
> Jens Henrik
>
> P.S:
> We have tested this with older ParaView versions, too (5.2.0 and 5.1.2) and
> got the same segfaults of Xorg of display 1.
> The only difference was, that ParaView 5.3.0 results in a segfault when
> connecting and ParaView 5.2.0+5.1.2 results in segfaults when loading data.
>
>
>
>
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>


More information about the Paraview-developers mailing list