Ctrl+Z Crash and file corruption while editing #43435

New Issue

Aurelio Barrios · 2015-01-27T19:12:22+01:00

Aurelio Barrios commented

2015-01-27 19:12:22 +01:00

System Information
Operating system and graphics card
OSX Yosemite (10.10.1), Intel Iris Pro 1536 MB and NVIDIA GeForce GT 750M

Blender Version
Broken: (2.73, b4d8fb5, Damaged .blend file tried also on 2.73a, bbf09d9 and 2.65)
Worked: (optional)

Short description of error
While editing a mesh, pressing ctrl+Z after exiting edit mode, crashes the file. 2 files have been corrupted, on 1 occasion file did not get corrupted.

Exact steps for others to reproduce the error
Open the attached .blend file (AT&T_Park.blend), select an object (f.ex the floor) > enter edit mode > manipulate a vertice > exit edit mode, press Ctrl+Z

The second attached blend file (AT&T_Park_DAMAGED.blend) crashes on my machine on startup.

{F139625}AT_T_Park_DAMAGED.blend

**System Information** Operating system and graphics card OSX Yosemite (10.10.1), Intel Iris Pro 1536 MB and NVIDIA GeForce GT 750M **Blender Version** Broken: (2.73, b4d8fb5, Damaged .blend file tried also on 2.73a, bbf09d9 and 2.65) Worked: (optional) **Short description of error** While editing a mesh, pressing ctrl+Z after exiting edit mode, crashes the file. 2 files have been corrupted, on 1 occasion file did not get corrupted. **Exact steps for others to reproduce the error** Open the attached .blend file (AT&T_Park.blend), select an object (f.ex the floor) > enter edit mode > manipulate a vertice > exit edit mode, press Ctrl+Z The second attached blend file (AT&T_Park_DAMAGED.blend) crashes on my machine on startup. {[F139625](https://archive.blender.org/developer/F139625/AT_T_Park.blend.zip)}[AT_T_Park_DAMAGED.blend](https://archive.blender.org/developer/F139623/AT_T_Park_DAMAGED.blend)

Aurelio Barrios commented

2015-01-27 19:12:22 +01:00

Changed status to: 'Open'

Aurelio Barrios commented

2015-01-27 19:12:22 +01:00

Added subscriber: @Aurelio-Barrios

Aurelio Barrios commented

2015-01-27 19:14:08 +01:00

This comment was removed by @Aurelio-Barrios

*This comment was removed by @Aurelio-Barrios*

Aurelio Barrios commented

2015-01-27 19:16:09 +01:00

Here the crash report if it is of any help:

crashreport_AT_T_Park_DAMAGED.txt

Here the crash report if it is of any help: [crashreport_AT_T_Park_DAMAGED.txt](https://archive.blender.org/developer/F139626/crashreport_AT_T_Park_DAMAGED.txt)

Aaron Carlisle commented

2015-01-27 20:54:17 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-01-27 20:54:17 +01:00

can confirm

Aurelio Barrios commented

2015-01-28 17:57:10 +01:00

I've just received information from a colleague who is working on the same files, that he had the same issue, when he enabled the "Texture Atlas" plugin that ships with blender. Here is what he wrote:

"I fiddled with the file and atlas a while ago and then it just closed and couldn't be opened anymore, same with the blend1 and autosaves. Blender would quit as soon as I tried to open it."

So the bug is most probably related to the very useful Texture Atlas plugin and blender 2.73. I have no issues on 2.72 anymore.

I've just received information from a colleague who is working on the same files, that he had the same issue, when he enabled the "Texture Atlas" plugin that ships with blender. Here is what he wrote: "I fiddled with the file and atlas a while ago and then it just closed and couldn't be opened anymore, same with the blend1 and autosaves. Blender would quit as soon as I tried to open it." So the bug is most probably related to the very useful Texture Atlas plugin and blender 2.73. I have no issues on 2.72 anymore.

Aaron Carlisle commented

2015-01-28 20:50:58 +01:00

so what happens when you disable the addon?

Julian Eisel commented

2015-02-02 01:27:40 +01:00

Added subscribers: @ideasman42, @JulianEisel

Julian Eisel commented

2015-02-02 01:27:40 +01:00

Can confirm here (with both files). Getting an failed assert which doesn't tell me much but looks like a memory issue:

  blender: malloc.c:2365: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.

@ideasman42 any clue here?

Can confirm here (with both files). Getting an failed assert which doesn't tell me much but looks like a memory issue: ``` blender: malloc.c:2365: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed. ``` @ideasman42 any clue here?

Sergey Sharybin commented

2015-02-03 14:25:14 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-02-03 14:25:14 +01:00

The files are just corrupted. I.e. first one has more than 8 UV maps, which should not happen.

@Aurelio-Barrios, we can not make corrupted files to work, but we should fix the root of the issue instead. For this we need to know exact steps of how you produced mesh with more than 8 UV maps.

The files are just corrupted. I.e. first one has more than 8 UV maps, which should not happen. @Aurelio-Barrios, we can not make corrupted files to work, but we should fix the root of the issue instead. For this we need to know exact steps of how you produced mesh with more than 8 UV maps.

Aurelio Barrios commented

2015-02-03 15:12:58 +01:00

In #43435#284707, @Blendify wrote:
so what happens when you disable the addon?

Hi Aaron,
I've opened Blender 2.73 again, disabled the Atlas addon, reproduced the steps with the same file and got the same results. So it crashes with and without this addon enabled.

> In #43435#284707, @Blendify wrote: > so what happens when you disable the addon? Hi Aaron, I've opened Blender 2.73 again, disabled the Atlas addon, reproduced the steps with the same file and got the same results. So it crashes with and without this addon enabled.

Aurelio Barrios commented

2015-02-03 15:25:48 +01:00

In #43435#286407, @Sergey wrote:
The files are just corrupted. I.e. first one has more than 8 UV maps, which should not happen.

@Aurelio-Barrios, we can not make corrupted files to work, but we should fix the root of the issue instead. For this we need to know exact steps of how you produced mesh with more than 8 UV maps.

Hello Sergey,

Those files have been exported as .dae files from Sketchup and imported into blender. The sketchup export is terrible, it creates tons of duplicated textures and vertices and hundreds of uvs. So I basically i used blender to clean up the model.

One update of success:
I've removed all uv textures with a custom script, and tried to reproduce the steps, now the file doesn't crash, even with the Texture Atlas addon enabled.

If there's anything else i can do, let me know. Btw. its the first time i'm experimenting Blender to crash! ;) so thanks for your hard work.

> In #43435#286407, @Sergey wrote: > The files are just corrupted. I.e. first one has more than 8 UV maps, which should not happen. > > @Aurelio-Barrios, we can not make corrupted files to work, but we should fix the root of the issue instead. For this we need to know exact steps of how you produced mesh with more than 8 UV maps. Hello Sergey, Those files have been exported as .dae files from Sketchup and imported into blender. The sketchup export is terrible, it creates tons of duplicated textures and vertices and hundreds of uvs. So I basically i used blender to clean up the model. One update of success: I've removed all uv textures with a custom script, and tried to reproduce the steps, now the file doesn't crash, even with the Texture Atlas addon enabled. If there's anything else i can do, let me know. Btw. its the first time i'm experimenting Blender to crash! ;) so thanks for your hard work.

Sergey Sharybin commented

2015-02-03 15:51:37 +01:00

It'll help having .dae which is exporting badly.

Aurelio Barrios commented

2015-02-03 16:08:45 +01:00

find attached the original collada file:

AT_T_Park.dae.zip

find attached the original collada file: [AT_T_Park.dae.zip](https://archive.blender.org/developer/F140682/AT_T_Park.dae.zip)

Gaia Clary was assigned by Sergey Sharybin

2015-02-03 16:19:13 +01:00

Sergey Sharybin commented

2015-02-03 16:19:13 +01:00

Added subscriber: @GaiaClary

Sergey Sharybin commented

2015-02-03 16:19:13 +01:00

@GaiaClary, are you around to look into this issue?

Julian Eisel commented

2015-03-08 19:19:45 +01:00

@GaiaClary, any news here? If you can't find a way to solve this, we should rather change this into a Todo

Gaia Clary commented

2015-03-09 01:07:24 +01:00

So i imported the file AT_T_Park.dae that was submit by aureliobk at 3-feb-2015
I used Blender #12f60e7

I get a ton of duplicate vertices and duplicate faces, but i do not get a crash.
I edited the meshes a bit, and that works as expected. I could not get Blender
to crash even after cleaning up the model for a couple of minutes.

So either this issue has been fixed with one of the recent collada changes
or i do not test exactly as i am supposed to test.

Please can you test on a daily blender build and give more detailed instructions for how to to reproduce the issue on a recent blender version?

So i imported the file AT_T_Park.dae that was submit by aureliobk at 3-feb-2015 I used Blender #12f60e7 I get a ton of duplicate vertices and duplicate faces, but i do not get a crash. I edited the meshes a bit, and that works as expected. I could not get Blender to crash even after cleaning up the model for a couple of minutes. So either this issue has been fixed with one of the recent collada changes or i do not test exactly as i am supposed to test. Please can you test on a daily blender build and give more detailed instructions for how to to reproduce the issue on a recent blender version?

Julian Eisel commented

2015-03-09 01:16:06 +01:00

Also can't recreate anymore.

Campbell Barton commented

2015-03-09 05:54:49 +01:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2015-03-09 05:54:49 +01:00

Campbell Barton commented

2015-03-09 05:54:49 +01:00

Over a week with no response, fixes have been made here (meshes now run validate) & devs cant redo.

closing.

Over a week with no response, fixes have been made here (meshes now run `validate`) & devs cant redo. closing.

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

Ctrl+Z Crash and file corruption while editing #43435