# Calling Render Seems to Crash pvpython
**URL:** https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102
**Category:** ParaView Support
**Tags:** python
**Created:** [December 21, 2020, 12:23am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102 "2020-12-21T00:23:43Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@suoarski](https://discourse.paraview.org/u/suoarski)
#### Post date: [December 21, 2020, 12:23am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/1 "2020-12-21T00:23:43Z")
So I have just installed ParaView, and decided to follow the tutorial _Introduction to Paraview_, on the official documentation for ParaView. Everything works fine, until I open pvpython 5.9.0, and run the following:
```
from paraview.simple import *
Sphere()
Show()
Render()
```
The display just crashes with no bug reports, and I have no idea why. It seems to work fine when I’m working using the User Interface, but only crashes when I’m using the python shell.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 21, 2020, 10:40am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/2 "2020-12-21T10:40:30Z")
Short answer: use `Interact()` instead of `Render()`. Press q to quit.
Long Answer: It is not crashed, just unresponding and your OS thinks it is crashed because of that. This is expected behavior with pvpython.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [December 21, 2020, 5:44pm UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/3 "2020-12-21T17:44:08Z")
I just tested on Linux, and the four commands listed worked fine… RC2…
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 21, 2020, 5:45pm UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/4 "2020-12-21T17:45:47Z")
@suoarski is confusing a non responding window with a crash. The window is indeed non responsive after a Render().
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [December 21, 2020, 5:56pm UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/5 "2020-12-21T17:56:24Z")
Again, on my setup (Linux, 5.9.0-RC2), the following commands do NOT crash and do NOT stop responding. Note also that the commands below are slightly incomplete. You don’t have a handle to the sphere.
from paraview.simple import \*
Sphere()
Show()
Render()
Hide()
Clip()
Show()
Render()
---
### Author:  [@suoarski](https://discourse.paraview.org/u/suoarski)
#### Post date: [December 22, 2020, 12:35am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/6 "2020-12-22T00:35:02Z")
Thank you, that does work, to some extent. After pressing ‘q’, the window becomes unresponsive afterwards. The terminal still works, and the display continues working once I call _Interact()_ again. I guess I was thrown off by the unresponsive window.
---
### Author:  [@suoarski](https://discourse.paraview.org/u/suoarski)
#### Post date: [December 22, 2020, 12:40am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/7 "2020-12-22T00:40:37Z")
Yeh, after messing around with it, the shell works as usual, but the display goes unresponsive (On Windows 10) whenever it’s not currently in _Interact()_ mode. I guess it could just be ignored, although it’s something that might be worth debugging eventually.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 22, 2020, 9:32am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/8 "2020-12-22T09:32:20Z")
The “unresponsive window” things is Microsoft Windows specific and not really an issue.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 22, 2020, 9:35am UTC](https://discourse.paraview.org/t/calling-render-seems-to-crash-pvpython/6102/9 "2020-12-22T09:35:35Z")
Not really “worth debugging” as we know exactly what causes this. The window is not answering any of the window manager attempt to communicate with it and this is how it was designed.
This was alreaddy answered by @utkarsh.ayachit in 2014 here:
>