<div dir="ltr">It seems that the workaround for this for now is to have users start their X servers with the “-noreset” option. Alternatively, you could use EGL enabled server executables and this will be totally overcome.<div><br></div><div>Utkarsh</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 13, 2017 at 12:11 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Let me try to contact NVidia developers and see if they can provide some info. What driver versions did you try this with?<span class="HOEnZb"><font color="#888888"><div><br></div><div>Utkarsh</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 11, 2017 at 9:34 AM, "Göbbert, Jens Henrik" <span dir="ltr"><<a href="mailto:j.goebbert@fz-juelich.de" target="_blank">j.goebbert@fz-juelich.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Utkarsh,<br>
<br>
you are right - I forgot to set the threshold to 0 before testing.<br>
Now it crashes when opening a new render view.<br>
<br>
We tested different versions of the NVIDIA driver already - they all behave the same way.<br>
Any hints how to track this error down?<br>
<br>
Best,<br>
Jens Henrik<br>
<span><br>
______________________________<wbr>__________<br>
From: Utkarsh Ayachit [<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>]<br>
</span>Sent: Thursday, May 11, 2017 3:21 PM<br>
<div class="m_1501721069280521981HOEnZb"><div class="m_1501721069280521981h5">To: Göbbert, Jens Henrik<br>
Cc: <a href="mailto:paraview-developers@paraview.org" target="_blank">paraview-developers@paraview.o<wbr>rg</a><br>
Subject: Re: [Paraview-developers] xdisplay-test + display=1 => segfault<br>
<br>
Jens,<br>
<br>
One final thing, can you ensure that you're doing remote rendering<br>
when you're closing/creating render views i.e. make sure your Remote<br>
Render Threshold is set to 0 before you try the test I suggested.<br>
<br>
On Thu, May 11, 2017 at 4:37 AM, "Göbbert, Jens Henrik"<br>
<<a href="mailto:j.goebbert@fz-juelich.de" target="_blank">j.goebbert@fz-juelich.de</a>> wrote:<br>
> Hello Utkarsh,<br>
><br>
> thank you for the hint.<br>
> I checked if ParaView/5.3.0 (connected to 12 pvservers on the same node) crashes, if I close the render view and open a new one. This is not the case - I can close and open render views multiple times without problems (as long as I have called pvserver with "--disable-xdisplay-test").<br>
><br>
> Best,<br>
> Jens Henrik<br>
><br>
> P.S:<br>
> In this context I would like to mention this bugreport:<br>
> If using VirtualGL and NVIDIA driver in non-GLVND style ParaView 5.3.0 segfaults on startup (even without pvservers).This is not the case with the driver in GLVND style.<br>
> "Segfault with ParaView 5.3.0RC2" - <a href="https://github.com/VirtualGL/virtualgl/issues/44" rel="noreferrer" target="_blank">https://github.com/VirtualGL/v<wbr>irtualgl/issues/44</a><br>
><br>
> ______________________________<wbr>__________<br>
> From: Utkarsh Ayachit [<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>]<br>
> Sent: Wednesday, May 10, 2017 7:24 PM<br>
> To: Göbbert, Jens Henrik<br>
> Cc: <a href="mailto:paraview-developers@paraview.org" target="_blank">paraview-developers@paraview.o<wbr>rg</a><br>
> Subject: Re: [Paraview-developers] xdisplay-test + display=1 => segfault<br>
><br>
> Jens,<br>
><br>
> Can you try closing current render view and creating new view? Does<br>
> that fail even when you pass `--disable-xdisplay-test`? In my<br>
> experience, whenever I have seen a crash in pvserver startup which can<br>
> be circumvented by `--disable-xdisplay-test`, it's been a driver bug<br>
> with creating multiple opengl contexts.<br>
><br>
> Utkarsh<br>
><br>
> On Wed, May 10, 2017 at 11:51 AM, "Göbbert, Jens Henrik"<br>
> <<a href="mailto:j.goebbert@fz-juelich.de" target="_blank">j.goebbert@fz-juelich.de</a>> wrote:<br>
>> Hello ParaView-Team,<br>
>><br>
>> we recently have experienced reproducible a segfaults of Xorg on display=1<br>
>> (on CentOS 7.2 server with two NVIDIA Tesla K40), when used with:<br>
>> --server--<br>
>> parallel ParaView/5.3.0 session (compiled with VTK_USE_X)<br>
>> over turboVNC(2.1.1) +VirtualGL(2.2.1)<br>
>> --client--<br>
>> from a Windows7 client<br>
>> with turboVNC(2.1.1)<br>
>> (other versions of turboVNC and VirtualGL led to the same<br>
>><br>
>> This crash does _NOT_ happen, if the vncviewer(yes: vncVIEWER!) is running<br>
>> on a Linux machine.<br>
>> As soon as ParaView GUI (running on the server with turboVNC+VirtualGL, too)<br>
>> connects to the pvservers running on the same machine, at least one of the<br>
>> pvservers on display=1 crashes (MPI leads then to a stop of the other<br>
>> pvservers).<br>
>> The crash of the pvserver on display 1 leads to a crash of Xorg of display 1<br>
>> - or it is the other way round.<br>
>><br>
>> We found that this crash can be avoided by starting the pvservers with the<br>
>> flag "--disable-xdisplay-test"<br>
>> I report this here, as it took some time to stumble over the flag<br>
>> "--disable-xdisplay-test" and this mail might help someone else.<br>
>> It seems as if the xdisplay-test is doing some nasty stuff ...<br>
>><br>
>> As this bug is related to the OS(=Windows) of the client running turboVNC<br>
>> the xdisplay-test might trigger a bug in turboVNC or Xorg itself...<br>
>><br>
>> Best,<br>
>> Jens Henrik<br>
>><br>
>> P.S:<br>
>> We have tested this with older ParaView versions, too (5.2.0 and 5.1.2) and<br>
>> got the same segfaults of Xorg of display 1.<br>
>> The only difference was, that ParaView 5.3.0 results in a segfault when<br>
>> connecting and ParaView 5.2.0+5.1.2 results in segfaults when loading data.<br>
>><br>
>><br>
>><br>
>><br>
>> ------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------<br>
>> ------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------<br>
>> Forschungszentrum Juelich GmbH<br>
>> 52425 Juelich<br>
>> Sitz der Gesellschaft: Juelich<br>
>> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498<br>
>> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher<br>
>> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),<br>
>> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,<br>
>> Prof. Dr. Sebastian M. Schmidt<br>
>> ------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------<br>
>> ------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------<br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
>><br>
>> Search the list archives at:<br>
>> <a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>Paraview-developers</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview-develope<wbr>rs</a><br>
>><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>