Frequent Crashes When Posing Bones? #69402

New Issue

Ovionis · 2019-09-02T09:25:09+02:00

Ovionis commented

2019-09-02 09:25:09 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-27 18:27, hash: 697fd86506

Short description of error
I've been continuously getting random crashes while using Blender.
I'm not sure if they ALL happen in Pose Mode but I know it started after the 2.80 release.

It's not specific to any one file I'm using and it doesn't happen after doing any one specific thing.

Error: EXCEPTION_ACCESS_VIOLATION
Address: 0x0000000140027721
Module: C:\Program Files\Blender Foundation\Blender\blender.exe

{F7713872 size=full}

While posing bones/rotating view/etc, Blender will pause for a quick second (like it's loading something), then when I try to do anything (move viewport), it just closes.

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64 **Blender Version** Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-27 18:27, hash: `697fd86506` **Short description of error** I've been continuously getting random crashes while using Blender. I'm not sure if they ALL happen in Pose Mode but I know it started after the 2.80 release. It's not specific to any one file I'm using and it doesn't happen after doing any one specific thing. ``` Error: EXCEPTION_ACCESS_VIOLATION Address: 0x0000000140027721 Module: C:\Program Files\Blender Foundation\Blender\blender.exe ``` {[F7713872](https://archive.blender.org/developer/F7713872/image.png) size=full} While posing bones/rotating view/etc, Blender will pause for a quick second *(like it's loading something)*, then when I try to do anything *(move viewport)*, it just closes.

Ovionis commented

2019-09-02 09:25:09 +02:00

Added subscriber: @Phigon

item412 commented

2019-09-04 17:30:04 +02:00

Added subscriber: @item412

Dalai Felinto commented

2019-09-17 19:00:41 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2019-09-17 19:00:41 +02:00

Thanks for the report. We need a file where things happen. Ideally before the issue is about to happen (as in, when you only need to move the bones around to see the issue).

Dalai Felinto commented

2019-09-17 19:01:15 +02:00

Also please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

Ovionis commented

2019-09-18 01:55:02 +02:00

Can you tell me how the error address can be used to diagnose a problem?

I understand how the module can be used, because if it were related to a .dll file then you could look there but the address is just a random number to me and the only thing I can use it for is finding when other people post the exact same number for their issues.
I'm the only one with this number, so that's useless.

When I crash, I've tried opening the recovery file and doing as much as I can remember doing before the crash but it just works this time and the crash occurs later.

There is no consistency in these crashes.
The only way I can probably get a file from before, is to save after every single thing I do.
Toggle pose mode > Save > select bone > Save > change properties category > save > toggle bone property > save.

I would have to do that for like 5-45 minutes, just to see if I can get a file that I could then go back to and do a couple of things before crashing again.

I ask about how to use the Address because a developer in a report I made before said it helps in diagnosing the problem but didn't clarify exactly how.

I'd like to use the address, read the code and see if I can get a good idea about what's happening internally before I crash, so that I can provide a consistent and reliable crash report.

Can you tell me how the error address can be used to diagnose a problem? I understand how the module can be used, because if it were related to a .dll file then you could look there but the address is just a random number to me and the only thing I can use it for is finding when other people post the exact same number for their issues. I'm the only one with this number, so that's useless. - - - -- When I crash, I've tried opening the recovery file and doing as much as I can remember doing before the crash but it just works this time and the crash occurs later. There is no consistency in these crashes. The only way I can probably get a file from before, is to save after every single thing I do. Toggle pose mode > Save > select bone > Save > change properties category > save > toggle bone property > save. I would have to do that for like 5-45 minutes, just to see if I can get a file that I could then go back to and do a couple of things before crashing again. - - -- I ask about how to use the Address because a developer in a report I made before said it helps in diagnosing the problem but didn't clarify exactly how. I'd like to use the address, read the code and see if I can get a good idea about what's happening internally before I crash, so that I can provide a ***consistent and reliable*** crash report.

Dalai Felinto commented

2019-09-18 02:04:06 +02:00

Can you tell me how the error address can be used to diagnose a problem?

I wouldn't know what to make of the "error address". But I guess technically you can use it to see if the issue is related to the HEAP or STACK memory.

Honestly what a developer would do is to build a Debug (or ReleaseWithDebugInfo) version of Blender, and upon crashing launching it in MSVC and get a backtrace of the problem, though that means a slower Blender and it requires the person to build Blender.

Also please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

I still need you to clear this up. This is to be sure you have no addon that may be causing this problem.

> Can you tell me how the error address can be used to diagnose a problem? I wouldn't know what to make of the "error address". But I guess technically you can use it to see if the issue is related to the HEAP or STACK memory. Honestly what a developer would do is to build a Debug (or ReleaseWithDebugInfo) version of Blender, and upon crashing launching it in MSVC and get a backtrace of the problem, though that means a slower Blender and it requires the person to build Blender. > Also please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue. I still need you to clear this up. This is to be sure you have no addon that may be causing this problem.

Ovionis commented

2019-09-18 05:27:25 +02:00

In #69402#778251, @dfelinto wrote:

Also please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

I still need you to clear this up. This is to be sure you have no addon that may be causing this problem.

I use addon(s) to make using Blender easier.
The crash doesn't occur all the time, it just happens.
If I were to disable all addons, I would still need to re-change numerous settings in the preferences.
Even then, that would ONLY prove that it happens without addons; it would yield no further information on how to actually make it crash in the first place.

For example, before I made this report 2 weeks ago, I crashed over 5 times.
I deleted my Blender versions from then (for space) but I still have the temporary files from then, including the last file before I gave up and decided to report.

I opened the file as well as used a version of my addon(s) from that day.
I'm moving bones around, running animation playback, selected/deselecting things, undo, etc, frequently to induce a crash.

Nohing's happening.
I only get this crash, when I'm not trying to get this crash.

> In #69402#778251, @dfelinto wrote: >> Also please go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue. > > I still need you to clear this up. This is to be sure you have no addon that may be causing this problem. I use addon(s) to make using Blender easier. The crash doesn't occur all the time, it just happens. If I were to disable all addons, I would still need to re-change numerous settings in the preferences. Even then, that would ONLY prove that it happens without addons; it would yield no further information on how to actually make it crash in the first place. For example, before I made this report 2 weeks ago, I crashed over 5 times. I deleted my Blender versions from then *(for space)* but I still have the temporary files from then, including the last file before I gave up and decided to report. I opened the file as well as used a version of my *addon(s)* from that day. I'm moving bones around, running animation playback, selected/deselecting things, undo, etc, frequently to induce a crash. Nohing's happening. I only get this crash, when I'm not trying to get this crash.

Ovionis commented

2019-09-26 23:20:51 +02:00

Changed status from 'Open' to: 'Resolved'

Ovionis closed this issue

2019-09-26 23:20:51 +02:00

Ovionis self-assigned this 2019-09-26 23:20:51 +02:00

Ovionis commented

2019-09-26 23:20:51 +02:00

Closing task for now, as I haven't got this crash in over a week and I don't have a Blender version where I did anymore either,
Will re-open if relapse.

Closing task for now, as I haven't got ***this*** crash in over a week and I don't have a Blender version where I did anymore either, Will re-open if relapse.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Frequent Crashes When Posing Bones? #69402