Weird first visualization

[felixveysseyre]

Hello,

Thanks to @jourdain , I was able to build my one visualizer base on ParaViewWeb npm package.
When used on a local computer (both Ubuntu and MacOS), everything is working smootly.

I tried to deploy my project on a g2.2xlarge AWS instance to test performances in real condition.
I had some hard time finding how to install X and nvidia drivers but thanks to this issue I finally succeed.

I tested my project and it seems to works correctly, nevertheless I always get some weird results for my very first connection (after I started the launcher).

Here are two screenshots representing what I got for my first connection and for any other connection:

I have looked into ParaViewWeb logs and nothing special appeared.

Here are some test cases:

Test1:

• Start launcher
• Start new connection: connection 1 -> weird
• Start new connection: connection 2 -> OK
• Start new connection: connection 3 -> OK

Test2:

• Start launcher
• Start new connection: connection 1 -> weird
• Close connection 1
• Start new connection: connection 2 -> OK
• Start new connection: connection 3 -> OK

Any idea guys ?

Thanks for your time !

[jourdain]

And interacting with the view does not fix the rendering issue?

[jourdain]

Which window manager did you install on the EC2 instance?

You may want to use offscreen rendering to see if that fix the issue.

Just need to add similar lines to your server 135+136

https://github.com/Kitware/light-viz/blob/master/server/light_viz_protocols.py#L135

[jourdain]

Moreover, did you picked the latest driver or did you simply use the link that was provided. Moreover did you double check the actual GPU?

[felixveysseyre]

Interacting with the view changes the view but it does not fix the issue:

I changed my code to render the view offscreen. The rendering is now done offscreen but the issue is still here.

When setting-up my EC2 instance, I installed the xserver-xorg package. Therefore I used X as window manager.

[felixveysseyre]

When setting-up my EC2 instance, I installed 340.46 nvidia drivers.

I tried more recent drivers (346 & 364) on other instances and I did get errors preventing me to use OpenGL correctly.

What do you advise to double check the GPU ?

[jourdain]

Don't know the command to show the hardware information.

Is any of the command line provided here provide that information in output?

[felixveysseyre]

The GPU available on my EC2 instance is GK104GL [GRID K520]

00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8]
00:03.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL [GRID K520] [10de:118a] (rev a1)

[jourdain]

this suggest to use the UI to download the right driver.

[felixveysseyre]

I did installed latest Nvidia drivers available (367.57) and it did not solve the issue.

Nevertheless I think I found the root of the issue.

I was starting X in a bad way:

sudo /usr/bin/X &

It was logging messages anywhere:

7 XSELINUXs still allocated at reset
SCREEN: 0 objects of 368 bytes = 0 total bytes 0 private allocs
COLORMAP: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 96 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 128 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 88 bytes = 0 total bytes 0 private allocs
PIXMAP: 2 objects of 120 bytes = 240 total bytes 0 private allocs
...

Rather than starting X that way, I am using now xinit:

sudo xinit &

Hope it will help someone !