Bugged Blend File? #51706

New Issue

Jakeb Ladrey · 2017-06-02T21:51:55+02:00

Jakeb Ladrey commented

2017-06-02 21:51:55 +02:00

System Information
Windows 10
AMD Radeon HD 8650G

Blender Version
Broken: 2.78c Windows 64, specific blend file(s)
Worked: 2.78c Windows 64, all other blend files

Short description of error

When attempting to open a specific blend file, blender closes. The blend had been working before. Debug says EXCEPTION_ACCESS_VIOLATION. Same crash happens if attempting to append or link to the same blend. Same crash happens with backup version of blend file. Same crash happens on completely different computer (Windows 7) when attempting to open the same bugged blend file.

More lengthy description here:
https://blender.stackexchange.com/questions/80642/is-this-any-hope-for-this-possibly-corrupted-blend-file

Exact steps for others to reproduce the error
File > Open > entervillains-mpg.blend

Link to bugged file here: https://drive.google.com/open?id=0B7KZpsOGSPLveFVEcDdlV2JfWlk
Link to folder with bugged back-up files and alternate file, plus 1 example NON-bugged blend file (intro-mpg): https://drive.google.com/drive/folders/0B7KZpsOGSPLvVnEyX2hldV9Rdms

**System Information** Windows 10 AMD Radeon HD 8650G **Blender Version** Broken: 2.78c Windows 64, specific blend file(s) Worked: 2.78c Windows 64, all other blend files **Short description of error** When attempting to open a specific blend file, blender closes. The blend had been working before. Debug says EXCEPTION_ACCESS_VIOLATION. Same crash happens if attempting to append or link to the same blend. Same crash happens with backup version of blend file. Same crash happens on completely different computer (Windows 7) when attempting to open the same bugged blend file. More lengthy description here: https://blender.stackexchange.com/questions/80642/is-this-any-hope-for-this-possibly-corrupted-blend-file **Exact steps for others to reproduce the error** File > Open > entervillains-mpg.blend Link to bugged file here: https://drive.google.com/open?id=0B7KZpsOGSPLveFVEcDdlV2JfWlk Link to folder with bugged back-up files and alternate file, plus 1 example NON-bugged blend file (intro-mpg): https://drive.google.com/drive/folders/0B7KZpsOGSPLvVnEyX2hldV9Rdms

Jakeb Ladrey commented

2017-06-02 21:51:55 +02:00

Changed status to: 'Open'

Jakeb Ladrey commented

2017-06-02 21:51:55 +02:00

Added subscriber: @JLL

Joel Godin commented

2017-06-03 02:39:27 +02:00

Added subscriber: @FloridaJo

Joel Godin commented

2017-06-03 02:39:27 +02:00

I'm on OSX. I was able to open the file, but there is no assets in them.
Not sure if you packed them before saving. But that may also be why it is not crashing for me.
I opened, tried to render a few frames, but no assets, no render.
I then saved the file. Try to open this saved file and see what happens.
FJ_entervillains-mpg.blend

I'm on OSX. I was able to open the file, but there is no assets in them. Not sure if you packed them before saving. But that may also be why it is not crashing for me. I opened, tried to render a few frames, but no assets, no render. I then saved the file. Try to open this saved file and see what happens. [FJ_entervillains-mpg.blend](https://archive.blender.org/developer/F616435/FJ_entervillains-mpg.blend)

Jakeb Ladrey commented

2017-06-03 03:07:15 +02:00

I had not packed the assets. (Apologies for not saying.)

I can open that saved file! It correctly paths to the audio portions but seems confused on the stills and video strips. [EDIT: It correctly paths the images and video as well, FJ's blend file simply had the UV Image Editor up instead of the VSE window.] As far as I'm concerned, personally, this solves my problem.

As far as what caused the bug in the first place, it's perhaps less useful of a solution, but I'm pleased that someone else on another system opening and then saving the file fixed the bug on this specific file.

I had not packed the assets. (Apologies for not saying.) I **can** open that saved file! It correctly paths to the audio portions but seems confused on the stills and video strips. [EDIT: It correctly paths the images and video as well, FJ's blend file simply had the UV Image Editor up instead of the VSE window.] As far as I'm concerned, personally, this solves my problem. As far as what caused the bug in the first place, it's perhaps less useful of a solution, but I'm pleased that someone else on another system opening and then saving the file fixed the bug on this specific file.

Fable Fox commented

2017-06-03 05:19:45 +02:00

Added subscriber: @fablefox

Fable Fox commented

2017-06-03 05:19:45 +02:00

It caused Blender to close on me. However, next time attached the blend file here instead of external file host.

Also, no crash log generated.

It caused Blender to close on me. However, next time attached the blend file here instead of external file host. Also, no crash log generated.

Joel Godin commented

2017-06-03 16:58:44 +02:00

What OS are you on @fablefox ?

Fable Fox commented

2017-06-03 20:53:21 +02:00

Windows 7 64 bit.

Ray molenkamp commented

2017-06-04 00:25:11 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-06-04 00:25:11 +02:00

@FloridaJo, please triage a little bit more careful in the future, just because the user is on windows, doesn't mean it's a windows specific issue.

This specific issue I can repro with a stock 2.78c on both windows and Linux.

The good news is, i can't repro it with a latest master build, so whatever the issue was is likely fixed already.

@fablefox try a nightly build from http://builder.blender.org to validate the issue is fixed for you.

@FloridaJo, please triage a little bit more careful in the future, just because the user is on windows, doesn't mean it's a windows specific issue. This specific issue I can repro with a stock 2.78c on both windows and Linux. The good news is, i can't repro it with a latest master build, so whatever the issue was is likely fixed already. @fablefox try a nightly build from http://builder.blender.org to validate the issue is fixed for you.

Fable Fox commented

2017-06-04 04:22:07 +02:00

The issue fixed for me with latest master build. I hope it also fixed for the OP, @JLL

I'm just trying to reproduce the issue.

The issue fixed for me with latest master build. I hope it also fixed for the OP, @JLL I'm just trying to reproduce the issue.

Bastien Montagne commented

2017-06-05 09:04:39 +02:00

Added subscriber: @mont29