# Linux X issues
**URL:** https://discourse.paraview.org/t/linux-x-issues/80
**Category:** Dashboards
**Created:** [June 4, 2018, 5:13pm UTC](https://discourse.paraview.org/t/linux-x-issues/80 "2018-06-04T17:13:44Z")
**Posts on this page:** 15
**Page:** 3
### Author:  [@shawn.waldon](https://discourse.paraview.org/u/shawn.waldon)
#### Post date: [June 22, 2018, 6:02pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/41 "2018-06-22T18:02:43Z")
I used ParaView master with VTK master (after your branch was merged).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 23, 2018, 3:31am UTC](https://discourse.paraview.org/t/linux-x-issues/80/42 "2018-06-23T03:31:32Z")
Thanks ! @shawn.waldon : could you do the same with Vall ?
---
### Author:  [@shawn.waldon](https://discourse.paraview.org/u/shawn.waldon)
#### Post date: [June 25, 2018, 5:39pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/43 "2018-06-25T17:39:50Z")
`vall` test (again this is ParaView master with VTK master):
Fedora 28, upgraded from previous versions (installed as 24 I think).
Quadro K420
Driver version: 396.24 (installed from this ppa: [https://negativo17.org/nvidia-driver/](https://negativo17.org/nvidia-driver/))
Kernel: 4.16.16-300
Xorg: 1.19.6
Qt: 5.9.2
Gnome: 3.28.2
Memory usage from nvidia-smi:
Before:
Global: 99MiB / 1996MiB
/usr/libexec/Xorg 32MiB
/usr/bin/gnome-shell 64MiB
After:
Global: 244MiB / 1996MiB
/usr/libexec/Xorg 125MiB
/usr/bin/gnome-shell 113MiB
edit: I will add that this is definitely the problem. When I went to run the test, I had to reboot vall since the display was locked (nvidia-smi before the reboot confirmed that all graphics memory was used up).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 26, 2018, 3:06am UTC](https://discourse.paraview.org/t/linux-x-issues/80/44 "2018-06-26T03:06:35Z")
@Michael @Joachim_Pouderoux : since you do not reproduce the bug, could you post your own results here ?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 26, 2018, 2:43pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/45 "2018-06-26T14:43:09Z")
@Joachim_Pouderoux I updated my results above with the ParaView and VTK SHA’s used.
---
### Author:  [@shawn.waldon](https://discourse.paraview.org/u/shawn.waldon)
#### Post date: [June 26, 2018, 5:35pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/46 "2018-06-26T17:35:55Z")
Update: from watching the dashboard as it tests builds and trying nvidia-smi on it:
A typical build of PV master leaks 500+MB of graphics memory. So the branch is a major improvement even if it doesn’t fix everything.
+1 for an update VTK branch to pull in the improvement.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 27, 2018, 2:27am UTC](https://discourse.paraview.org/t/linux-x-issues/80/47 "2018-06-27T02:27:04Z")
The MR is already up but another fix seems to break a single test test on ista. We are looking into it.
[paraview/paraview!2511](https://gitlab.kitware.com/paraview/paraview/merge_requests/2511)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 27, 2018, 7:46am UTC](https://discourse.paraview.org/t/linux-x-issues/80/48 "2018-06-27T07:46:31Z")
> [@shawn.waldon](#):
>
> I think tylo’s issue has to do with the power outage last night. It is not on a UPS and it doesn’t handle reboots well.
Tylo seems to fail again, could you check it’s memory ?
---
### Author:  [@Joachim\_Pouderoux](https://discourse.paraview.org/u/Joachim_Pouderoux)
#### Post date: [July 1, 2018, 2:23pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/49 "2018-07-01T14:23:02Z")
`shark` test (ParaView master with VTK master (on July 1st)):
Xubuntu 18.04
GeForce GTX 660
4K Screen resolution
Driver version: 390.48
Kernel: 4.15.0-20
Xorg: 1.19.6
Qt: 5.9.5
Xfce 4.12 with Compositor ENABLED
Memory usage from nvidia-smi:
Before:
Global: 302MiB / 1999MiB
After:
Global: 582MiB / 1999MiB
> LEAK!
PS: I did not compile PV with testing enable to build it faster so I use the following command line:
`for i in {1..20}; do bin/paraview --test-script=/path_to_paraview_sources/Applications/ParaView/Testing/XML/UndoRedo2.xml --exit; done`
For info I used a minimal ParaView build: TEST=OFF, MPI=OFF, Python=OFF, all\_PLUGINS=OFF, Catalyst=OFF
If I turn off the Compositor (xfwm4-tweaks-settings):
> NO LEAK!
Attached is a simple test that leaks.
[simple.xml](https://discourse.paraview.org/uploads/default/original/1X/86648b8d30f2ad0ac89df1de8afd9f820e76de4c.xml) (695 Bytes)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 3, 2018, 7:25am UTC](https://discourse.paraview.org/t/linux-x-issues/80/51 "2018-07-03T07:25:53Z")
Guys, after a rigourous round of tests, the issue is now always reproducible whatever the configuration.
I will keep investigating.
In the meantime, the different fixes that have landed on master recently should limit a little bit the leak.
In any case, if we want to have working buildbot we will need to restart X regularly until this is fixed.
I will manage luigi, but vall (and tylo?) will need to be managed from your side.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 12, 2018, 7:29am UTC](https://discourse.paraview.org/t/linux-x-issues/80/52 "2018-07-12T07:29:51Z")
Fixed It !
Caused by a Qt Issue and an incorrect null parenting before deletion in pqMultiViewWidget.
See Qt [issue](https://bugreports.qt.io/browse/QTBUG-69429) and [MR](https://gitlab.kitware.com/paraview/paraview/merge_requests/2581).
(I am so happy right now 😀🤣😃😄😆)
---
### Author:  [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [July 12, 2018, 8:22am UTC](https://discourse.paraview.org/t/linux-x-issues/80/53 "2018-07-12T08:22:40Z")
Congratulations! 👍
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [July 12, 2018, 12:08pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/54 "2018-07-12T12:08:15Z")
Awesome! Thanks for persisting!
---
### Author:  [@Joachim\_Pouderoux](https://discourse.paraview.org/u/Joachim_Pouderoux)
#### Post date: [July 12, 2018, 1:25pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/55 "2018-07-12T13:25:12Z")
🙈 🎉🎉🎉
---
### Author:  [@shawn.waldon](https://discourse.paraview.org/u/shawn.waldon)
#### Post date: [July 12, 2018, 1:27pm UTC](https://discourse.paraview.org/t/linux-x-issues/80/56 "2018-07-12T13:27:18Z")
🎉 🎉 🎉
[Previous page](https://discourse.paraview.org/t/linux-x-issues/80.md?page=2)