EXCEPTION_ACCESS_VIOLATION, Seemingly random crash #114626

New Issue

Marek-Polivka · 2023-11-08T11:54:49+01:00

Marek-Polivka commented

2023-11-08 11:54:49 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23

Blender Version
Broken: version: 3.6.5, branch: blender-v3.6-release, commit date: 2023-10-16 14:30, hash: cf1e1ed46b7e
Worked: 3.4 maybe. I had a similar crash for a while

Short description of error
Blender crashes with:
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7BD3D5A98
Module : blender.exe
Thread : 00001970

I believe it happens on somewhat complex files (hundreds of objects, hundred thousands to a few million tris). Blender crashes a few minutes after starting up and working on a project.

I tried lowering undo steps (had 128, set to 64) but it didn't change.

Exact steps for others to reproduce the error
I don't know how to reproduce it. I have a suspicion it crashes upon an undo but I undo often and it works normally until it crashes.
I'm also sorry for not being able to include the .blend file. It's company policy I have no control over unfortunately.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23 **Blender Version** Broken: version: 3.6.5, branch: blender-v3.6-release, commit date: 2023-10-16 14:30, hash: `cf1e1ed46b7e` Worked: 3.4 maybe. I had a similar crash for a while **Short description of error** Blender crashes with: Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF7BD3D5A98 Module : blender.exe Thread : 00001970 I believe it happens on somewhat complex files (hundreds of objects, hundred thousands to a few million tris). Blender crashes a few minutes after starting up and working on a project. I tried lowering undo steps (had 128, set to 64) but it didn't change. **Exact steps for others to reproduce the error** I don't know how to reproduce it. I have a suspicion it crashes upon an undo but I undo often and it works normally until it crashes. I'm also sorry for not being able to include the .blend file. It's company policy I have no control over unfortunately.

VimperkCastle.crash.txt

50 KiB

Marek-Polivka added the

labels 2023-11-08 11:54:50 +01:00

Germano Cavalcante commented

2023-11-08 14:23:42 +01:00

Unfortunately, we can't fix issue, that is random.
The Crash Log shows that the crash occurred when Undoing the move operation in edit mode. But it's still not clear why it crashed.
Could it be that the file is corrupt?
Could it be that Blender ran out of memory?

I would advise to try alpha build from https://builder.blender.org/download/daily/ and perhaps make screen recording of this issue.
Ultimately, I would expect a particular .blend file and/or particular set of steps to trigger this issue.

Unfortunately, we can't fix issue, that is random. The Crash Log shows that the crash occurred when Undoing the move operation in edit mode. But it's still not clear why it crashed. Could it be that the file is corrupt? Could it be that Blender ran out of memory? I would advise to try alpha build from https://builder.blender.org/download/daily/ and perhaps make screen recording of this issue. Ultimately, I would expect a particular .blend file and/or particular set of steps to trigger this issue.

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-11-08 14:23:52 +01:00

Marek-Polivka commented

2023-11-08 17:01:40 +01:00

I don't think it's a lack of memory. I have 64GB and even during the crash, the usage was 26 GB (Blender is only a little part of it, something around 500 MB)

Whether the file is corrupt I don't know. It runs and doesn't seem to crash on touching anything particular. Is there a way to check?

I'll give a shot to the newer builds tomorrow. I'll let you know how that went.

I don't think it's a lack of memory. I have 64GB and even during the crash, the usage was 26 GB (Blender is only a little part of it, something around 500 MB) Whether the file is corrupt I don't know. It runs and doesn't seem to crash on touching anything particular. Is there a way to check? I'll give a shot to the newer builds tomorrow. I'll let you know how that went.

Marek-Polivka commented

2023-11-20 10:43:02 +01:00

I've tried switching to 4.0.0 stable for a while but the crash is still there. I unfortunately can't go with newer versions because some tools I need aren't compatible with it yet so I at least need to maintain compatibility with 3.6*.

I've seen a suggestion somewhere to start a new project and append objects from the old one if it's corrupted somehow so I'll try that.

I've tried switching to 4.0.0 stable for a while but the crash is still there. I unfortunately can't go with newer versions because some tools I need aren't compatible with it yet so I at least need to maintain compatibility with 3.6*. I've seen a suggestion somewhere to start a new project and append objects from the old one if it's corrupted somehow so I'll try that.

Pratik Borhade commented

2023-12-14 10:37:54 +01:00

Whether the file is corrupt I don't know. It runs and doesn't seem to crash on touching anything particular. Is there a way to check?

Loop over all meshes present in the scene and run mesh.validate() operator to check whether any mesh data is corrupted: https://docs.blender.org/api/current/bpy.types.Mesh.html#bpy.types.Mesh.validate

> Whether the file is corrupt I don't know. It runs and doesn't seem to crash on touching anything particular. Is there a way to check? Loop over all meshes present in the scene and run mesh.validate() operator to check whether any mesh data is corrupted: https://docs.blender.org/api/current/bpy.types.Mesh.html#bpy.types.Mesh.validate

Marek-Polivka commented

2023-12-18 17:15:02 +01:00

I've tried that and 2 objects apparently got fixed. Subsequent runs reported nothing. Unfortunately it crashed again a few minutes later while I was trying if it still crashed.

Pratik Borhade commented

2023-12-19 05:15:49 +01:00

Any luck with factory settings?: File > Defaults > Load Factory Settings -> ctrl+o -> open affected .blend file

Any luck with factory settings?: `File > Defaults > Load Factory Settings` -> ctrl+o -> open affected .blend file

Marek-Polivka commented

2023-12-19 13:19:42 +01:00

Unfortunately no, factory settings don't change the issue.

Pratik Borhade commented

2023-12-20 05:05:03 +01:00

Thanks. Not much we will be able to help without example file
From function calls, I suspect crash possibly occurred due to accessing the pointer that is null or points to freed memory (bm->CustomData)

I'm not sure but does op->py_instance suggest operator is written in python? @mano-wii

Thanks. Not much we will be able to help without example file From function calls, I suspect crash possibly occurred due to accessing the pointer that is null or points to freed memory (`bm->CustomData`) I'm not sure but does `op->py_instance` suggest operator is written in python? @mano-wii

Germano Cavalcante commented

2023-12-20 14:13:44 +01:00

I'm not sure but does op->py_instance suggest operator is written in python?

Nice catch! The op->py_instance indeed suggests that the operator involved in the crash is written in Python. However, it seems challenging to identify the specific operator or the root cause of the issue. The crash log indicates that the bpy.ops.mesh.hidesato_offset_edges operator, possibly from an add-on, could be causing the crash. However, even with the add-on disabled (using Factory Settings), the issue still persists.

@Marek-Polivka, while sharing the .blend file is not possible, it would be tremendously helpful if you could simplify the file and provide a detailed description of the steps to reproduce the crash. Alternatively, if you can modify the .blend file by removing any elements that would violate company policy, you may share the modified file.

Without additional information, it might be challenging to pinpoint the exact cause of the crash. If we are unable to replicate the issue, we might end up spending a lot of time trying random guesses.

Another option is to try debugging the issue yourself by building Blender from source. However, please note that this requires technical knowledge and can be time-consuming.

> I'm not sure but does op->py_instance suggest operator is written in python? Nice catch! The `op->py_instance` indeed suggests that the operator involved in the crash is written in Python. However, it seems challenging to identify the specific operator or the root cause of the issue. The crash log indicates that the `bpy.ops.mesh.hidesato_offset_edges` operator, possibly from an add-on, could be causing the crash. However, even with the add-on disabled (using Factory Settings), the issue still persists. @Marek-Polivka, while sharing the .blend file is not possible, it would be tremendously helpful if you could simplify the file and provide a detailed description of the steps to reproduce the crash. Alternatively, if you can modify the .blend file by removing any elements that would violate company policy, you may share the modified file. Without additional information, it might be challenging to pinpoint the exact cause of the crash. If we are unable to replicate the issue, we might end up spending a lot of time trying random guesses. Another option is to try debugging the issue yourself by [building Blender](https://wiki.blender.org/wiki/Building_Blender) from source. However, please note that this requires technical knowledge and can be time-consuming.

Marek-Polivka commented

2023-12-20 16:08:20 +01:00

re: Hidesato offset edges... That could be the thing potentially. When I reset to the factory settings, I've then reinstalled this and ZenUV because both are pretty crucial in my workflow (sorry, I understood the reason to revert to factory settings being to reset potential forgotten settings and I stupidly thought that these 2 addons didn't matter). I'm pretty sure it doesn't only happen when I use the offset edges tool but maybe it's related anyway.

I've also not updated this one in a while and there's a newer version so all this could be my fault in the end - a mismatch between Blender version and the Offset Edges addon version. I'll go try out some versions or even omitting it and I'll report back with the results after a few hours if it crashes and maybe later tomorrow if it won't.

re: Hidesato offset edges... That could be the thing potentially. When I reset to the factory settings, I've then reinstalled this and ZenUV because both are pretty crucial in my workflow (sorry, I understood the reason to revert to factory settings being to reset potential forgotten settings and I stupidly thought that these 2 addons didn't matter). I'm pretty sure it doesn't only happen when I use the offset edges tool but maybe it's related anyway. I've also not updated this one in a while and there's a newer version so all this could be my fault in the end - a mismatch between Blender version and the Offset Edges addon version. I'll go try out some versions or even omitting it and I'll report back with the results after a few hours if it crashes and maybe later tomorrow if it won't.

Marek-Polivka commented

2023-12-20 16:12:03 +01:00

Turns out it's now included in Blender within Edit Mesh Tools so I'll turn that on instead of the external Offset Edges addon.

Pratik Borhade commented

2023-12-21 12:29:15 +01:00

It is possible that external Offset Edges addon has the missing 'UNDO' flag.
Guess we can close the report since culprit is likely third party add-on.
Feel free to reopen/comment if you have more relevant information to share.

It is possible that `external Offset Edges addon` has the missing 'UNDO' flag. Guess we can close the report since culprit is likely third party add-on. Feel free to reopen/comment if you have more relevant information to share.

Pratik Borhade closed this issue

2023-12-21 12:29:18 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-12-21 12:29:20 +01:00

Sign in to join this conversation.