# Interact() crash the second time in pvpython
**URL:** https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984
**Category:** ParaView Support
**Created:** [November 15, 2019, 2:34pm UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984 "2019-11-15T14:34:41Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@maria\_vlas](https://discourse.paraview.org/u/maria_vlas)
#### Post date: [November 15, 2019, 2:34pm UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984/1 "2019-11-15T14:34:41Z")
I’m using pvpython trying to replicate (without much success) work than in ParaView.
Right now I’m having trouble with pvpython and the funcion Iteract(), after closing the interact windows it doesn’t open again. Is this correct? How can I do this?
```auto
➜ ~ /Applications/ParaView-5.7.0.app/Contents/bin/pvpython ; exit;
Python 2.7.10 (default, Feb 22 2019, 21:55:15)
[GCC 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.37.14)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from paraview.simple import *
>>> cylinder2 = Cylinder()
>>> cylinder2.Resolution = 6
>>> cylinder2.Height = 1.0
>>> cylinder2.Radius = 0.5
>>> cylinder2.Center = [0.0, 0.0, 0.0]
>>> cylinder2.Capping = 1
>>> renderView1 = GetActiveViewOrCreate('RenderView')
>>> cylinder2Display = Show(cylinder2, renderView1)
>>> Interact()
>>> cylinder2.Resolution = 50
>>> Interact()
```
In mac I don’t get any message error, in Windows 10 I get
```auto
ERROR: In C:\bbd\6519e7fe\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 491
vtkShaderProgram (00000190C6D2E400): Shader object was not initialized, cannot attach it.
Generic Warning: In C:\bbd\6519e7fe\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLRenderTimer.cxx, line 124
vtkOpenGLRenderTimer::Stop called before vtkOpenGLRenderTimer::Start. Ignoring.
ERROR: In C:\bbd\6519e7fe\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 491
vtkShaderProgram (00000190C6D2D320): Shader object was not initialized, cannot attach it.
ERROR: In C:\bbd\6519e7fe\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLVertexArrayObject.cxx, line 280
vtkOpenGLVertexArrayObject (00000190C74323F0): attempt to add attribute without a program for attribute ndCoordIn
Generic Warning: In C:\bbd\6519e7fe\build\superbuild\paraview\src\VTK\Rendering\OpenGL2\vtkOpenGLQuadHelper.cxx, line 60
Error binding ndCoords to VAO.
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 18, 2019, 10:30am UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984/2 "2019-11-18T10:30:34Z")
I can’t reproduce on Linux.
@cory.quammen
---
### Author:  [@maria\_vlas](https://discourse.paraview.org/u/maria_vlas)
#### Post date: [November 18, 2019, 2:08pm UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984/3 "2019-11-18T14:08:57Z")
More Info: this was tested with pvpython that comes with ParaView 5.6.2 in Windows 10 and with the pvpython that comes with ParaView 5.7 in mac with the same result
---
### Author:  [@maria\_vlas](https://discourse.paraview.org/u/maria_vlas)
#### Post date: [November 18, 2019, 7:06pm UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984/4 "2019-11-18T19:06:26Z")
Okay. If I press ‘q’ on the windows and do something like
```auto
render_window = renderView1.GetRenderWindow()
render_window.Finalize()
```
then I can do Interact() again. I guess this is the desired behavior.
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [November 18, 2019, 9:34pm UTC](https://discourse.paraview.org/t/interact-crash-the-second-time-in-pvpython/2984/5 "2019-11-18T21:34:38Z")
> [@maria\_vlas](#):
>
> closing the interact windows it doesn’t open again.
Closing the window is indeed not supported currently. You can quit the interactor loop – as you discovered – by hitting the **q** key. The `window.Finalize` call should not be necessary.