Page MenuHome

Blender 2.8 (like 2.79) crashes when exporting to collada
Open, Needs Triage by DeveloperPublic

Description

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: rB2eead4868834
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.

Details

Type
Bug

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.EditedThu, Sep 26, 2:52 PM

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

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.

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.

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?

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.

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

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

Michael Lorrey (MikeLorrey) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Sat, Oct 5, 10:27 PM