Login  Register

Re: NEWT window takes ~10 sec to become visible on multiple monitor setups

Posted by Sven Gothel on Dec 23, 2014; 4:10pm
URL: https://forum.jogamp.org/NEWT-window-takes-10-sec-to-become-visible-on-multiple-monitor-setups-tp4033582p4033813.html

On 12/23/2014 11:47 AM, asambol [via jogamp] wrote:

>     gouessej wrote
>     Look at EnumDisplayDevices().
>
> I tried calling EnumDisplayDevices() in a seperate project and it runs
> perfectly fast (a few ms), so I guess that's not the bottleneck. The source
> code for that test is in the first answer here:
> http://stackoverflow.com/questions/9524309/enumdisplaydevices-function-not-working-for-me
>
> I tried running my test code with -Dnewt.verbose=true -Dnewt.debug=true and
> here is the output (not sure if anything looks suspicious there):
> http://pastebin.com/q3gQJWMy
>
> ">>> 3735" is printed right after glWindow.setVisible(true) and it's the
> miliseconds from start of program. For 3 monitors connected thats around 4
> seconds.
As mentioned earlier, setVisible is blocking (polling) until visibility
is reached.

Using one of our unit tests
  <http://forum.jogamp.org/NEWT-window-takes-10-sec-to-become-visible-on-multiple-monitor-setups-tp4033582p4033590.html>
might be a good idea to allow reproduction.

However you find the culprit in your setup,
it will be a great help for users w/ a similar issue, of course.

You may also see my comment about generic 'bring-up' performance here:
  <http://forum.jogamp.org/Quick-Requirements-Test-td4033768.html#a4033769>

>
> BTW, I tried with a Windows 8.1 machine and it seems the problem is gone, the
> window shows up in about 1 second for 3 monitors connected. Got to test more
> to confirm Windows 7 is the issue.
>
> I will try to build NEWT native dll's with some debug outputs enabled to
> identify the bottleneck line of code.

Thank you very much!

~Sven


signature.asc (828 bytes) Download Attachment