osltoy QLayout error when you hit the "Recompile" button

16 views
Skip to first unread message

etheory

unread,
Mar 5, 2020, 1:51:24 AM3/5/20
to OSL Developers
Hi there!

When I compile OpenShadingLanguage-1.10.9 with the following dependencies:
  • OpenImageIO-2.1.11.0
  • Qt_vfx-5.12.6
  • OpenEXR-2.4.0
on CentOS Linux release 7.4.1708 (Core)

When I launch it like so:
  • gdb --args osltoy shaders/mandelbrot.osl

and then hit "Recompile", I get the following error/segfault:

QLayout: Attempting to add QLayout "" to OSL_v1_10::OSLToyMainWindow "", which already has a layout
Thread 2 "osltoy" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd7557700 (LWP 215165)]
0x000000000041b6e4 in std::_Function_handler<void (int), OpenImageIO_v2_1::thread_pool::push<OSL_v1_10::OSLToyMainWindow::timed_rerender_trigger()::$_0>(OSL_v1_10::OSLToyMainWindow::timed_rerender_trigger()::$_0&&)::{lambda(int)#1}>::_M_invoke(std::_Any_data const&, int&&) ()

Is anyone else getting a similar issue, and if so, any ideas how to solve it?

Thanks!
Luke

Sam Hodge at GMail

unread,
Mar 5, 2020, 10:43:13 AM3/5/20
to osl...@googlegroups.com
Let me google that for you Luke


Seems you need a QWidget in between the QMainWindow and the QLayout.

Does it do the same thing with all shaders you throw at otoy, or is it specific to Mandelbrot?

I haven’t tried it out but it sounds interesting, I will see if I can spin up a development context similar to yours and give it a try.

Sam

--
You received this message because you are subscribed to the Google Groups "OSL Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osl-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osl-dev/53e42115-1182-4263-ab41-3be40778cc81%40googlegroups.com.

Luke Emrose

unread,
Mar 5, 2020, 5:19:13 PM3/5/20
to osl...@googlegroups.com
Hi Sam!

Nice to hear from you.

Yes of course I googled it. I even tried to fix it in the source code but I wasn't successful. Since this is in the OSL source itself I assumed I'd done something wrong and other people had this working.

All shaders show this behavior in my setup that was just my example case.

Cheers,
L


You received this message because you are subscribed to a topic in the Google Groups "OSL Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osl-dev/QnhO0Ntr1qo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osl-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osl-dev/CAJ3WgDxByzc%2B-sD%3DEF0FuD8cKnGM0gwpQ1agMNa3F0smS7iv8g%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages