# Render() or Interact() + q make the window unresponsive

**URL:** https://discourse.paraview.org/t/render-or-interact-q-make-the-window-unresponsive/4673
**Category:** ParaView Support
**Tags:** python
**Created:** [June 24, 2020, 7:14pm UTC](https://discourse.paraview.org/t/render-or-interact-q-make-the-window-unresponsive/4673 "2020-06-24T19:14:39Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![lukor](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/l/aca169/32.png) [@lukor](https://discourse.paraview.org/u/lukor)
#### Post date: [June 24, 2020, 7:14pm UTC](https://discourse.paraview.org/t/render-or-interact-q-make-the-window-unresponsive/4673/1 "2020-06-24T19:14:39Z")

</div>

I’m using the Python ParaView package (v5.7.0) from within Spyder in Windows, using the built-in iPython console to run my scripts. When I run `Interact()`, the visualization and interaction works well, but when I quit out of it by pressing `q`, the window stops responding. If I instead run Render(), the same thing happens.

Is there any way to keep this from happening? Force-quitting the window causes the iPython kernel to restart, sometimes incorrectly, which adds additional friction to the workflow.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [December 22, 2020, 9:34am UTC](https://discourse.paraview.org/t/render-or-interact-q-make-the-window-unresponsive/4673/2 "2020-12-22T09:34:11Z")

</div>

Just ignore it.