question

Daniel Mikolajcak avatar image
Daniel Mikolajcak asked ·

Frequent crashing during rendering

Hello guys,

I have a big scene that experiences frequent rendering crashing, would you please have a look at bug report what I may do to make Cinema more stabel?

_BugReport.txt

bugcrashing
-bugreport.txt (475.3 KiB)
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Daniel Mikolajcak avatar image
Daniel Mikolajcak answered ·

Now it crashes but no reference to texture, only this message I don't understand:

00:00:32 11619MB ERROR| signal caught: SIGFPE -- Floating point exception


25 comments
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

It's a pretty generic message. It could be many things.
It could be a bug, but what triggers the bug?

All these texture errors are a concern...did you try with Ignore Textures, as a test?

0 Likes 0 ·

Since it crashes on occasion I always save the scene and take a risk of crash. I have tight deadline, I cannot afford extensive testing without textures. As for right now all errors are gone. Seems like Arnold is picky what textures it accepts.

0 Likes 0 ·

What could this error mean Stephen?

00:00:21 9307MB ERROR| [texturesys] /Cow_Skin|image: Not a TIFF or MDI file, bad magic number 12150 (0x2f76) (filename = "sksprql_4K_Normal.tx")

00:00:21 9307MB ERROR| [texturesys] /Cow_Skin|image_3: Not a TIFF or MDI file, bad magic number 12150 (0x2f76) (filename = "sksprql_4K_Albedo.tx")

0 Likes 0 ·

This suggests your .tx file might be corrupted.

Are you getting the same error message each time or is it different? If it's random seeming, with it sometimes working, sometimes not, maybe this could be a symptom of bad hardware? If it's the same, can you supply a broken .tx file for us to look at?

0 Likes 0 ·
Show more comments

I checked ignore textures and crashing stoppet. As soon as I turned them back on c4d crashed. So something about textures I guess:
Arnold Log:

00:00:13 7647MB WARNING| [AiMakeTx] OpenEXR "dwaa" compression has a bug for monochrome images, using "zip" instead

"/Cams___Lights/Cam_C_Dolomiten_Suite/Plane_6", but there is no opacity metadata for some of its shaders

00:00:15 7680MB ERROR| signal caught: SIGABRT -- Abnormal process abort

0 Likes 0 ·

Those are just warnings/info messages. The first one comes from the auto-tx, where we have to use a different compression to avoid a bug in OpenEXR.

The second is just telling you that some object has Opaque off, even though none of its shaders are making it transparent.

The ERROR is a generic crash message, so we still don't know what's happening to cause the crash.

0 Likes 0 ·
Show more comments
Daniel Mikolajcak avatar image
Daniel Mikolajcak answered ·

**UPDATE**
Opened the .jpg in Affinity and changed color profile from sRGB IESC61966-2.1 to generic RGB. now error is not appearing.

**UPDATE**

00:00:19 7248MB ERROR| [texturesys] /Inox|oaktramonto597267-edit_2: /Volumes/Samsung_X5/materials/Metal/Smooth Metal/Textures/Smooth Metal 3/Metal_009_NRM_6K.tx

00:00:23 7250MB ERROR| signal caught: SIGFPE -- Floating point exception

Hi guys, I get frequent crashes during rendering. I pasted report from Log. It points to this texture which seem to be fine. I don't see an obvious issue there.

1 comment
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Hmm, errors have returned, same textures:

C4DtoA | 00:00:14 9563MB ERROR| [texturesys] /Smooth_Metal_Aluminium_Dark|oaktramonto597267-edit_2: /Volumes/Samsung_X5/materials/Metal/Smooth Metal/Textures/Smooth Metal 3/Metal_009_NRM_6K.tx

C4DtoA | 00:00:14 9563MB ERROR| [texturesys] /Smooth_Metal_Aluminium_Dark|oaktramonto597267-edit: unspecified OIIO error (filename = "Metal_009_COL_6K.tx")

0 Likes 0 ·
Stephen Blair avatar image
Stephen Blair answered ·

Maybe it is texture related.

        Call_Stack_Thread_123145790861312
        {
            libai.dylib:    0x11fcf391b (SP: 0x70001d1e6810, PC: 0x11fcf391b)
            libai.dylib:    0x11fdc0202 (SP: 0x70001d1e6af0, PC: 0x11fdc0202)
            libai.dylib:    0x11fdbee88 (SP: 0x70001d1e6c50, PC: 0x11fdbee88)
            libai.dylib:    0x11fdbd5a7 (SP: 0x70001d1e6d60, PC: 0x11fdbd5a7)
            libai.dylib:    _AiTextureHandleAccess + 0x109f (SP: 0x121c86df0, PC: 0x1209e8cff)

Any chance you could post a detailed Arnold log?https://docs.arnoldrenderer.com/display/A5AFCUG/Log


As a test: If you ignore textures, do you still crash?

9 comments
10 |600 characters needed characters left characters exceeded

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Hello Stephen,

What do you mean ignoring textures? Do you mean "abort on error" option?
Daniel

Arnold Log.txt

0 Likes 0 ·
arnold-log.txt (4.3 KiB)

this could be causing the crashes, but no idea why, does arnold have pronlem with tif format?
00:00:32 16808MB ERROR| [c4dtoa] Failed to generate 66 TX files:

00:00:32 16808MB ERROR| [c4dtoa] /Library/Application Support/Laubwerk/Plants/Howea_forsteriana/textures/Howea_forsteriana_lf_03_co.tif

...

0 Likes 0 ·

You'll find the Ignore textures option in the render settings. You can also try to disable auto tx, not sure it helps though.

Can you send us one of the failing textures?

0 Likes 0 ·

https://we.tl/t-aFBKdCGwgh
I uploaded one of the TIF 's, I suspect they are the bad apples.

0 Likes 0 ·

This texture works fine for me, the tx file is generated properly. Which version of C4DtoA do you use? I tried the latest 3.0.3.

0 Likes 0 ·

I use latest version too, I think crashes were caused by too many instances made by plugin Surface spread 2. After reducing number of them, Arnold stoped crashing.

Error reports such as:"ERROR: Could not open "/Library/Application Support/Laubwerk/Plants/Howea_forsteriana/textures/Howea_forsteriana_lf_03_co.96a628fd.temp.tx"" still puzzle me however.

Anyway let's call it as solved

0 Likes 0 ·
Show more comments
Show more comments

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Welcome to the Arnold Answers community.

This is the place for Arnold renderer users everywhere to ask and answer rendering questions, and share knowledge about using Arnold, Arnold plugins, workflows and developing tools with Arnold.

If you are a new user to Arnold Answers, please first check out our FAQ and User Guide for more information.

When posting questions, please be sure to select the appropriate Space for your Arnold plugin and include the plugin version you are using.

Please include images, scene and log files whenever possible as this helps the community answer your questions.

Instructions for generating full verbosity log files are available for MtoA, MaxtoA, C4DtoA, HtoA, KtoA, and Kick.

If you are looking for Arnold Documentation and Support please visit the Arnold Support site.

To try Arnold please visit the Arnold Trial page.

Bottom No panel present for this section.