Page MenuHome

Bake from Multires on Displacement mode exits Blender when Preview level is on 0
Closed, ResolvedPublic

Description

System Information
Ubuntu 13.04 / NV 580 3GB with proprietary driver

Blender Version
Broken: Blender 2.6X r61240 (today's Buildbot)
Worked: Blender 2.69 r60991 (last stable)

Short description of error
Bake from Multires on Displacement mode exits Blender when Preview level is on 0. I want to make a point here : when I said "exits" it really exits with no error code, no "crash".

Exact steps for others to reproduce the error
I made the simplest possible test. New file, UV Unwrap the default cube, add a Multires modifier, subdivide to 4, use the Sculpt Mode to do what you want, then set the Preview setting to 0. Assign a new empty Image to it in the UV/Image Editor. Go to Render context, Bake panel, set the mode to Displacement, enable Bake from Multires tick, hit the Bake button and here it goes : EXIT.

Test file

Event Timeline

Mickaël Guédon (ebrain) raised the priority of this task from to Needs Triage by Developer.
Mickaël Guédon (ebrain) updated the task description. (Show Details)
Mickaël Guédon (ebrain) set Type to Bug.

Confirmed, seems to be division by zero, assigning to sergey.

Crashed Thread:  20

Exception Type:  EXC_ARITHMETIC (SIGFPE)
Exception Codes: EXC_I386_DIV (divide by zero)

Thread 20 Crashed:
0   org.blenderfoundation.blender 	0x000000010be8fdad get_ccgdm_data + 141
1   org.blenderfoundation.blender 	0x000000010be8ea4f apply_heights_callback + 399
2   org.blenderfoundation.blender 	0x000000010be90822 flush_pixel + 818
3   org.blenderfoundation.blender 	0x000000010be90bd5 rasterize_half + 469
4   org.blenderfoundation.blender 	0x000000010be903c5 do_multires_bake_thread + 837
5   libsystem_c.dylib             	0x00007fff86db57a2 _pthread_start + 327
6   libsystem_c.dylib             	0x00007fff86da21e1 thread_start + 13
Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Confirmed, Medium.Nov 16 2013, 5:16 PM

It is fixed now, thanks for the report!