Closed GoogleCodeExporter closed 9 years ago
I'll be spending time on the issue this week.
Original comment by aintergu...@gmail.com
on 7 Dec 2011 at 4:38
Original comment by aintergu...@gmail.com
on 7 Dec 2011 at 4:38
Great,
Got a bit more info for you.
It's crashing in the CoralNetworkNode::compute method on line 121:
std::string attrName = inPlug.partialName().asChar();
It looks like the partialName method is failing.
Also before the crash proper, there was an exception that corrupted the Maya
channel box UI:
First-chance exception at 0x75e5b9bc in maya.exe: Microsoft C++ exception:
TfileException at memory location 0x0144f3ac..
Keir
Original comment by keirr...@gmail.com
on 7 Dec 2011 at 8:35
Hi, it looks like I can't repro the issue here, it's all working fine.
Do you think you could try fixing it on your side?
Maybe checking if inPlug is valid, or doing std::cout << inPlug.partialName()
to see if that crashes as well.
Original comment by aintergu...@gmail.com
on 9 Dec 2011 at 3:04
Hey,
Thanks for looking into it for me.
I will try to do some more testing later in the week. I was going to do it this
morning but I managed to introduce a linker error when building the plugin :)
Keir
Original comment by keirr...@gmail.com
on 13 Dec 2011 at 1:59
Right so the crash is definitely happening when looking up the name of the
plug. I tried both partialName and name methods. I also dropped a status check
on the isNull call, to see if it was silently failing (it wasn't).
Keir
Original comment by keirr...@gmail.com
on 14 Dec 2011 at 11:07
So wait a sec, you are saying the plug is not null and yet it crashes when
asked for the name?
Original comment by aintergu...@gmail.com
on 15 Dec 2011 at 8:01
Yes, it passes the null plug check and then crashes.
Original comment by keirr...@gmail.com
on 15 Dec 2011 at 8:22
I think I was able to repro this issue using maya's Attribute Editor rather
than the Channel Box.
Original comment by aintergu...@gmail.com
on 2 Jan 2012 at 8:55
This should now be fixed.
Original comment by aintergu...@gmail.com
on 3 Jan 2012 at 11:05
Original issue reported on code.google.com by
keirr...@gmail.com
on 28 Nov 2011 at 8:47