Reported by Andrew@IE:
I've attached 2 example ops that are causing the unexpected errors/crashes on
the OpHolder.
derivedFromImagePrimOp-1.py crashes Houdini as soon as I select it from the op
path menu parameter. It sends the following error to my terminal:
terminate called after throwing an instance of
'IECore::InvalidArgumentException'
what(): ImagePrimitive: Cannot set displayWindow to the empty window
(sent by pid 9682)Internal abort
The error is being thrown by ImagPrimitive::setDisplayWindow(), but I'm not
sure why that's getting called on op creation. I've run the op external to
Houdini without setting any parameters and all works fine, with no such
exception being thrown...
raisesPythonException-1.py is meant to raise an Exception when operating.
However, the exception is raised (and sent to my python shell if visible, and
the node errors saying "Error raised during Python evaluation!") as soon as I
select it from the op path menu parameter (even if the OpHolder is not in the
currently displayed SOP chain). The exception continues to be raised every time
I left or middle click on the OpHolder. Locking, templating, or displaying the
node raises the exception, though bypassing and un-bypassing does not (unless
it's also displaying). Plugging the output into another node (which isn't
displaying) also raises the exception, and all the equivalent clicks on that
new node also raise the exception.
Original issue reported on code.google.com by danbeth...@gmail.com on 18 Sep 2010 at 9:47
Original issue reported on code.google.com by
danbeth...@gmail.comon 18 Sep 2010 at 9:47Attachments: