Page MenuHome

blender 2.80 and 2.81 crashes when i tried to copy a surf sub modifier.
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-7-6.1.7600-SP0 64 Bits
Graphics card: Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits) VMware, Inc. 3.3 (Core Profile) Mesa 11.2.0 (git-aa91c51)

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e and 2.81 beta eba4a4bd73ba date 2019-11-15 16:32

blender 2.81 crashes when i tried to copy a surf sub modifier with 6 level of viewport subvisions (i guess that its the limit per modifier) and then it immediately crashed when i clicked copy button. i simply tried this with a default cube so no nothing special to upload here...

Event Timeline

Michael Colina (MichaelBenDavid) renamed this task from blender280 and 2.81 crashes when i tried to copy a surf sub modifier. to blender 2.80 and 2.81 crashes when i tried to copy a surf sub modifier..Nov 19 2019, 7:50 PM

If you take a level-6 sub-d modifier and copy it, to make another level-6, that's a very dense mesh. Over 100 million faces if you start with a cube. My 32gb PC cannot do it; crashes after maxing out memory for a bit. (2 level 5's are ok and I can then bump one of them to level 6, but not both)

Just tried it once but the crash I see happens here:
MeshExtract_PosNor_Data.vbo_data looks bogus. It's possible the allocation for that array has failed due to OOM. Other allocations may fail randomly at other places if it's indeed out of memory.

blender.exe!extract_pos_nor_loop_mesh(const MeshRenderData * mr, int l, const MLoop * mloop, int UNUSED_p, const MPoly * UNUSED_mpoly, void * _data) Line 1439	C
[Inline Frame] blender.exe!mesh_extract_iter(const MeshRenderData * mr, const eMRIterType iter_type, int end, int extract, const MeshExtract * user_data, void *) Line 4221	C
blender.exe!extract_run(TaskPool * UNUSED_pool, void * taskdata, int UNUSED_threadid) Line 4244	C
blender.exe!task_scheduler_thread_run(void * thread_p) Line 454	C
Philipp Oeser (lichtwerk) changed the task status from Unknown Status to Unknown Status.Nov 20 2019, 10:02 AM
Philipp Oeser (lichtwerk) claimed this task.

Thanks for the report. It appears this crashes because Blender ran out of memory.

While we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug.