Image sequence crashing Tweet

[nickson]

Hi all,

Having another issue with loading image sequence textures, scrubbing along the timeline crashes maya almost instantly. Loading the same sequences in the standard maya file node works fine but alas not the octane one. Tried all different file types but still getting the same results. (running 2.24.2, osx 10.10.5, maya 2016 ext 1 sp6)

Excerpt from the crash log:

4 libGL.dylib 0x00007fff94e306a7 glPixelStorei + 18
5 OctanePlugin.bundle 0x000000014ce09323 OctaneItem::UpdateImageTexNode(OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, bool) + 1411
6 OctanePlugin.bundle 0x000000014ce10d84 OctaneItem::SetImageTex(OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, OctaneItem&, bool) + 292
7 OctanePlugin.bundle 0x000000014cdd0224 NodeRGBImageTexture::compute(MPlug const&, MDataBlock&) + 2212
8 libOpenMaya.dylib 0x0000000129c430c0 libOpenMaya.dylib + 1376448
9 libDependEngine.dylib 0x0000000107999cac std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 161372
10 libDependEngine.dylib 0x000000010799a2e2 std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 162962
11 libtbb.dylib 0x000000011184ed05 tbb::interface7::internal::task_arena_base::internal_execute(tbb::interface7::internal::delegate_base&) const + 325
12 libDependEngine.dylib 0x000000010799d1f2 std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 175010
13 libDependEngine.dylib 0x0000000107991662 std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 126994
14 libtbb.dylib 0x0000000111853d83 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 531
15 libtbb.dylib 0x0000000111853b48 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::wait_for_all(tbb::task&, tbb::task*) + 56
16 libDependEngine.dylib 0x00000001079a9a86 std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 226358
17 libDependEngine.dylib 0x00000001079a9b58 std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 226568
18 libDependEngine.dylib 0x000000010799537d std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 142637
19 libDependEngine.dylib 0x00000001079953bf std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*) + 142703
20 libsystem_pthread.dylib 0x00007fff98e1405a _pthread_body + 131
21 libsystem_pthread.dylib 0x00007fff98e13fd7 _pthread_body + 0
22 libsystem_pthread.dylib 0x00007fff98e113ed thread_start + 13

[nickson]

[calus]

Hi nickson,

I'm not sure if the crash happen while IPR running or when the animated texture displays in viewport.

If this is a viewport issue, to avoid the crash, you could override in viewport the octane shader with a maya shader, using this script :
viewtopic.php?f=28&t=52995&p=266550#p266550

[nickson]

Cheers calus,

Sadly not, it happens in all different viewport renderers, happens even without selecting octane as the renderer, just the image node itself crashes maya when playing or moving along the timeline.

Its been 5 days since I posted this, really losing any hope with Otoy.

[calus]

Are you using the 7.24 version of the plugin ?
I can't find any issue in octane texture image sequence, with the 2.24.2 - 7.24 plugin on windows .

Maybe it's a MacOS specific bug,
but it's strange nobody talked about this sooner.

Can you share a scene as simple as possible but still crashing ?

[k.a.schubert]

I'm testing a v2 for maya 2017 on OSX build tomorrow and will see if I can reproduce this bug.

[nickson]

Cheers Kai,

I tried recreating the crash on my macbook pro (also on 10.10.5), but i can't even get to that stage, maya crashes when I simply make an octane material.

//current scene = unDisclosed
//====================================================
//command history (most recent last):
//====================================================
//last tool: nurbsSelect
//====================================================
//panel with focus: nodeEditorPanel1
//visible panels:
// modelPanel4 nodeEditorPanel1
//====================================================
4 libsystem_kernel.dylib 0x00007fff99d6b136 __psynch_cvwait + 10
5 liboctane.dylib 0x000000014fc6173e boost::exception_detail::error_info_injector<boost::thread_resource_error>::error_info_injector(boost::exception_detail::error_info_injector<boost::thread_resource_error> const&) + 1054526
6 liboctane.dylib 0x000000014fbbb52d boost::exception_detail::error_info_injector<boost::thread_resource_error>::error_info_injector(boost::exception_detail::error_info_injector<boost::thread_resource_error> const&) + 374061
7 liboctane.dylib 0x000000014fb2251c liboctane.dylib + 832796
8 OctanePlugin.bundle 0x000000014f7ee81b NodeMaterial::renderSwatchImage(MImage&) + 363
9 libOpenMayaUI.dylib 0x00000001450bcdd8 libOpenMayaUI.dylib + 409048
10 libOpenMayaRender.dylib 0x000000013095e553 libOpenMayaRender.dylib + 116051
11 libSharedUI.dylib 0x000000010faa7303 libSharedUI.dylib + 709379
12 libSharedUI.dylib 0x000000010faa7a9a libSharedUI.dylib + 711322
13 libExtensionLayer.dylib 0x000000010acb06c6 libExtensionLayer.dylib + 112326
14 libExtensionLayer.dylib 0x000000010acb047a libExtensionLayer.dylib + 111738
15 QtCore 0x0000000112f28323 QObject::event(QEvent*) + 51
16 libExtensionLayer.dylib 0x000000010acb037a libExtensionLayer.dylib + 111482
17 QtGui 0x0000000113298849 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 265
18 QtGui 0x0000000113299f7f QApplication::notify(QObject*, QEvent*) + 879
19 libExtensionLayer.dylib 0x000000010aca7483 libExtensionLayer.dylib + 74883
20 QtCore 0x0000000112f154b6 QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
21 QtGui 0x000000011329c24d qt_sendSpontaneousEvent(QObject*, QEvent*) + 45
22 QtGui 0x000000011324af75 QEventDispatcherMacPrivate::activateTimer(__CFRunLoopTimer*, void*) + 197
23 CoreFoundation 0x00007fff918c42e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
24 CoreFoundation 0x00007fff918c3f73 __CFRunLoopDoTimer + 1059
25 CoreFoundation 0x00007fff9193753d __CFRunLoopDoTimers + 301
26 CoreFoundation 0x00007fff9187f608 __CFRunLoopRun + 2024
27 CoreFoundation 0x00007fff9187ebd8 CFRunLoopRunSpecific + 296
28 HIToolbox 0x00007fff92e6d56f RunCurrentEventLoopInMode + 235
29 HIToolbox 0x00007fff92e6d2ea ReceiveNextEventCommon + 431
30 HIToolbox 0x00007fff92e6d12b _BlockUntilNextEventMatchingListInModeWithFilter + 71
31 AppKit 0x00007fff96fae8ab _DPSNextEvent + 978
32 AppKit 0x00007fff96fade58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
33 AppKit 0x00007fff96fa3af3 -[NSApplication run] + 594
34 QtGui 0x000000011324c205 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1781
35 QtCore 0x0000000112f1284d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
36 QtCore 0x0000000112f15a67 QCoreApplication::exec() + 199
37 libExtensionLayer.dylib 0x000000010aca56e8 libExtensionLayer.dylib + 67304
38 Maya 0x000000010964800a Maya + 73738
39 Maya 0x0000000109659e8d Maya + 147085
40 libdyld.dylib 0x00007fff958fa5c9 start + 1

[calus]

but what is the exact version of your plugin ?

Is it 2.24.2-7.14
or 2.24.2- 7.24
or another version ?

[haze]

An update on this issue: we have also reproduced the crash on Linux and we have gathered enough information to lodge a ticket with Autodesk, as it seems this is related to the expression used on the Frame Extension attribute in the image texture node. Thanks for your patience while we wait to hear from Autodesk

[nickson]

An update on this issue: we have also reproduced the crash on Linux and we have gathered enough information to lodge a ticket with Autodesk, as it seems this is related to the expression used on the Frame Extension attribute in the image texture node. Thanks for your patience while we wait to hear from Autodesk

Cheers!