Linux application crashing
We are running Autodesk Maya 8.5 (64 bit) on opensuse 10 and 10.1 (both 64 bit OS) on 400 servers. These servers comprise of HP proliant blade server and IBM x336 series 1U servers.
These servers are configured as render farms for distributed processing (rendering) of maya scenes. The job distribution and scheduling is carried out by a third party software. Maya scenes are comprised of multiple frames. Each frame is rendered on individual server.
Of late we are facing an issue of maya crashing with multiple errors. But the errors are intermittent and the same frame gets rendered on the same server after resubmission.
Error 1 :
*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x00002aab18cf9010 ***
257.log:*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x000000001624faa0 ***
257.log:*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x00002aab1999f010 ***
maya encountered a fatal error
Signal: 11 (Unknown Signal)
MDataBlock::inputArrayValue(MObject const&, MStatus*)
shaveHairShape::compute(MPlug const&, MDataBlock&)
THsurfaceShape::computePlug(Tplug const&, TdataBlock&)
Tplug::getValue(TdataHandle&, TdataBlock const&, bool, bool, bool) const
TdependNode::getPlugValue(Tplug const&, TdataHandle&, TdgContext const&)
MPlug::getValue(float&, MDGContext&) const
initTexInfoLookup(MObjectArray const&, MString, bool, bool)
shaveRenderer::doShutter(MTime const&, shaveConstant::ShutterState)
Fatal Error. Attempting to save in /usr/tmp/render.20090430.0112.ma
Writing crash report in /usr/tmp/render.20090430.0112.crash
// Maya exited with status 1
What could these error mean and how can I troubleshoot them ? I have added following environment variables in /etc/profile for more details on the error.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development