Blender 2.8 (like 2.79) crashes when exporting to collada #70263

New Issue

Michael Lorrey · 2019-09-26T07:21:54+02:00

Michael Lorrey commented

2019-09-26 07:21:54 +02:00

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 965M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.59

Blender Version
Broken: version: 2.80 (sub 50), branch: master, commit date: 2019-03-19 21:25, hash: 2eead48688
Worked: (optional)

Short description of error
If I have had Blender open for some amount of hours (I have no way of calculating this because its so random), and I try to export to collada, blender crashes.

Exact steps for others to reproduce the error
Have blender open with some file that you've edited and saved for several hours.
File > Export > Collada
Give it a name. Hit Export

[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
Happens with many blender files.
Blender crash handling needs to give users the ability to report the data of the crash during the crash.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 965M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.59 **Blender Version** Broken: version: 2.80 (sub 50), branch: master, commit date: 2019-03-19 21:25, hash: `2eead48688` Worked: (optional) **Short description of error** If I have had Blender open for some amount of hours (I have no way of calculating this because its so random), and I try to export to collada, blender crashes. **Exact steps for others to reproduce the error** Have blender open with some file that you've edited and saved for several hours. File > Export > Collada Give it a name. Hit Export [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] Happens with many blender files. Blender crash handling needs to give users the ability to report the data of the crash during the crash.

Michael Lorrey commented

2019-09-26 07:21:54 +02:00

Added subscriber: @MikeLorrey

Brecht Van Lommel commented

2019-09-26 14:52:32 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-09-26 14:52:32 +02:00

We require an example .blend file to reproduce the issue, a crash log would not be enough information to investigate the issue.

Michael Lorrey commented

2019-09-26 19:12:48 +02:00

It happens with ANY blender file open for more than several hours. I keep blender open all day every day as I use it all the time. If I've had the blender file open for, say, four to six hours, its guaranteed to crash, but if blender itself has been open for more than that, and I open another file, it will also crash if i export from the newly opened file. Again, does not matter what file it is. The only factor is time that blender has been open. the crash on collada export creates a collada file of 0kb memory. I have included several examples of the crash collada output file using several sources. Note this problem also existed under Blender 2.79. Some of these files were created with that version, the newer two were made by 2.80 in the current build I'm using. Nor is this problem unique to the computer I am using now, it exists also on my desktop running Windows 8 with blender 2.78.
spiral-staircase10x9meters.dae

ymir-statue.dae

rubiks-cube-display.dae

Falcon1ER-Wyvern-stack.dae

It happens with ANY blender file open for more than several hours. I keep blender open all day every day as I use it all the time. If I've had the blender file open for, say, four to six hours, its guaranteed to crash, but if blender itself has been open for more than that, and I open another file, it will also crash if i export from the newly opened file. Again, does not matter what file it is. The only factor is time that blender has been open. the crash on collada export creates a collada file of 0kb memory. I have included several examples of the crash collada output file using several sources. Note this problem also existed under Blender 2.79. Some of these files were created with that version, the newer two were made by 2.80 in the current build I'm using. Nor is this problem unique to the computer I am using now, it exists also on my desktop running Windows 8 with blender 2.78. [spiral-staircase10x9meters.dae](https://archive.blender.org/developer/F7776026/spiral-staircase10x9meters.dae) [ymir-statue.dae](https://archive.blender.org/developer/F7776025/ymir-statue.dae) [rubiks-cube-display.dae](https://archive.blender.org/developer/F7776024/rubiks-cube-display.dae) [Falcon1ER-Wyvern-stack.dae](https://archive.blender.org/developer/F7776023/Falcon1ER-Wyvern-stack.dae)

Brecht Van Lommel commented

2019-09-27 02:21:41 +02:00

I understand it happens for all of your .blend files, but the factor is very unlikely to be time, but rather some operation that you are likely to perform in that time.

We need more exact steps to reproduce, we do not have time to spend many hours doing operations in Blender in the hope that this will let us reproduce the problem.

I understand it happens for all of your .blend files, but the factor is very unlikely to be time, but rather some operation that you are likely to perform in that time. We need more exact steps to reproduce, we do not have time to spend many hours doing operations in Blender in the hope that this will let us reproduce the problem.

Michael Lorrey commented

2019-09-27 03:18:12 +02:00

Its pretty basic, I use normal mesh editing functions to create and edit meshes, I create materials, map the UVs, it doesnt matter whether I assign textures or not, it doesn't matter whether its a new or old file. I'm a pretty keen observer and there is no common denominator other than that I'm exporting to collada with SL/OS static operator presets after several hours of the application operating, regardless of how much or how little work I do on the blender file. It crashes and creates a 0 byte file for the export file. Like I said, I know this is hard the lack of any sort of crash logging makes this difficult to debug. Are there any logs I can access despite the crash?

Michael Lorrey commented

2019-09-29 00:02:59 +02:00

Ok attached is a Jedi temple I worked on last night, left open all night, I just saved it, then went to export it to collada, and blender 2.8 crashed. I'm including both the blender file and the 0byte dae.Naboo Jedi Temple.blend

Naboo Jedi Temple.dae

Once again, a crash handler/log system would be great....

Ok attached is a Jedi temple I worked on last night, left open all night, I just saved it, then went to export it to collada, and blender 2.8 crashed. I'm including both the blender file and the 0byte dae.[Naboo Jedi Temple.blend](https://archive.blender.org/developer/F7778994/Naboo__Jedi_Temple.blend) [Naboo Jedi Temple.dae](https://archive.blender.org/developer/F7778993/Naboo__Jedi_Temple.dae) Once again, a crash handler/log system would be great....

Michael Lorrey commented

2019-09-29 00:03:48 +02:00

do you want i should upload a user preferences file if there is one here?

Philipp Oeser commented

2020-01-20 15:04:36 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-20 15:04:36 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2020-01-20 15:04:36 +01:00

Hi and thx for the report (sorry this has been lying around for so long...)

No crash here with Naboo Jedi Temple.blend exporting to collada [but my instance of blender has not been open for hours...].
More or less stabs in the dark, but:

does this also happen with other exporters?
does this happen with particular locations on your filesystem (if saving the .blend works, can you export in that same directory)?
do you have any Addons running that might interfere here? (Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue)
does this happen on other computers as well?
does this still happen in a fresh build from https://builder.blender.org/download/?
if you use a build from above, starting blender_debug_log.cmd (located in the extracted folder) and attaching blender_debug_output.txt here could help...

Hi and thx for the report (sorry this has been lying around for so long...) No crash here with `Naboo Jedi Temple.blend` exporting to collada [but my instance of blender has not been open for hours...]. More or less stabs in the dark, but: - does this also happen with other exporters? - does this happen with particular locations on your filesystem (if saving the .blend works, can you export in that same directory)? - do you have any Addons running that might interfere here? (Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue) - does this happen on other computers as well? - does this still happen in a fresh build from https://builder.blender.org/download/? - if you use a build from above, starting `blender_debug_log.cmd` (located in the extracted folder) and attaching `blender_debug_output.txt` here could help...

Michael Lorrey commented

2020-01-21 19:06:59 +01:00

No it doesn't happen with other exporters, that I can tell. I don't use other exporters normally, but have not had issues with them when i've used them.
No particular location. If I save the blend file, exporting is still a crapshoot by some parameter that seems to be time based, as if just sitting here for a few hours accumulates some unsaved log data despite no actual changes being made to the file.
I have a few addons, but this problem predates them. I have since installed newer versions of Blender and this export bug does not exhibit in the newer versions, though there is another export bug with 2.8 and 2.81a in that if I save changes to a mesh in edit mode, and immediately export to collada, the changes made since the last save/export are not included in the new export UNLESS I first go to Object mode and back to edit, and then export. This switch of modes from edit to object seems to update some sort of buffer that is used to export from. (again, this mode switch export bug is for the newer versions of blender, not 2.79, but they may be related to this 2.79 bug)
Yes, it happens on my other computer as well in version 2.79. I have not installed newer versions of blender on that computer either.
No, as specified in (3) it doesn't crash in newer versions of blender, but those have their own bug in not exporting any newer changes to collada unless I switch from edit mode to object mode before saving and exporting, so this may be related.
I will look at that. Thanks, I was wondering why the default download does not include a crash debug log/reporting system like many other applications do.

1) No it doesn't happen with other exporters, that I can tell. I don't use other exporters normally, but have not had issues with them when i've used them. 2) No particular location. If I save the blend file, exporting is still a crapshoot by some parameter that seems to be time based, as if just sitting here for a few hours accumulates some unsaved log data despite no actual changes being made to the file. 3) I have a few addons, but this problem predates them. I have since installed newer versions of Blender and this export bug does not exhibit in the newer versions, though there is another export bug with 2.8 and 2.81a in that if I save changes to a mesh in edit mode, and immediately export to collada, the changes made since the last save/export are not included in the new export UNLESS I first go to Object mode and back to edit, and then export. This switch of modes from edit to object seems to update some sort of buffer that is used to export from. (again, this mode switch export bug is for the newer versions of blender, not 2.79, but they may be related to this 2.79 bug) 4) Yes, it happens on my other computer as well in version 2.79. I have not installed newer versions of blender on that computer either. 5) No, as specified in (3) it doesn't crash in newer versions of blender, but those have their own bug in not exporting any newer changes to collada unless I switch from edit mode to object mode before saving and exporting, so this may be related. 6) I will look at that. Thanks, I was wondering why the default download does not include a crash debug log/reporting system like many other applications do.

Michael Lorrey commented

2020-01-21 19:11:01 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Jacques Lucke commented

2020-01-22 12:03:10 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-01-22 12:03:10 +01:00

Changed status from 'Needs Triage' to: 'Resolved'

Jacques Lucke closed this issue

2020-01-22 12:03:10 +01:00

Jacques Lucke self-assigned this 2020-01-22 12:03:10 +01:00

Jacques Lucke commented

2020-01-22 12:03:10 +01:00

If I understand this correctly, the original bug is fixed by now. So I'll close this report.

The other issue you describe might or might not be related. In any case, it would be better, if you create a separate report for it. Otherwise it will be confusing what this report is actually about.

Running this script in your file indicates that there is some invalid geometry:

import bpy

for ob in bpy.data.objects:
    if ob.type == "MESH":
        ob.data.validate(verbose=True)

BKE_mesh_validate_arrays:     Edge 83850: is a duplicate of 59683

If I understand this correctly, the original bug is fixed by now. So I'll close this report. The other issue you describe might or might not be related. In any case, it would be better, if you create a separate report for it. Otherwise it will be confusing what this report is actually about. Running this script in your file indicates that there is some invalid geometry: ``` import bpy for ob in bpy.data.objects: if ob.type == "MESH": ob.data.validate(verbose=True) ``` ``` BKE_mesh_validate_arrays: Edge 83850: is a duplicate of 59683 ```

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

Blender 2.8 (like 2.79) crashes when exporting to collada #70263