a pooltoy, Charge, Cradle, Echo, Kharaya-do, Luna, Meredith, Sevens, Sparkles, Spoke, Taliesenn, Tanwen/Tanwyn, UMBRA. and Vivi


Plural

ΘΔ

Autistic, ADHD

Nonbinary, Genderqueer, Trans

Kinky Ace, Demi, Bisexual


Weasyl (Visual Art and Commissions Archive)
www.weasyl.com/~faealchemist
pronouns.cc (WIP)
pronouns.cc/@FaeAlchemist
🗡️pleasepraise.me
pleasepraise.me/Kharaya-drone
🪀pleasepraise.me
pleasepraise.me/Cradle
Neocities (Personal Site)
faealchemist.neocities.org/

Dvorakir
@Dvorakir
a T-posing floragato in blender

was working on a macro scene today when blender would crash with an EXCEPTION_ACCESS_VIOLATION whenever I tried to render the scene.
"odd" I thought, because the scene worked just fine with viewport rendering.
the crash log stack trace gave a clue to where the issue was:

Stack trace:
blender.exe         :0x00007FF76C89A770  BKE_mesh_face_offsets_ensure_alloc
blender.exe         :0x00007FF76C89BC20  BKE_mesh_new_nomain
blender.exe         :0x00007FF76D7EB300  blender::geometry::execute_realize_mesh_tasks
blender.exe         :0x00007FF76D7F1290  blender::geometry::realize_instances
blender.exe         :0x00007FF76F143BE0  blender::nodes::node_geo_realize_instances_cc::node_geo_exec
blender.exe         :0x00007FF76CF41B10  blender::nodes::LazyFunctionForGeometryNode::execute_impl
[...]

ah yes, Realize Instances
some of the nodegraphs in the scene definitely use that node somewhere, so I started troubleshooting: disabling and deleting individual collections until the crash no longer occurred on render.


Seven-Cute-Fish
@Seven-Cute-Fish
This page's posts are visible only to users who are logged in.

You must log in to comment.