Blender freezing eternally upon exporting scene to Collada, FBX, OBJ etc. [MacOS Catalina] #76083

Open
opened 2020-04-25 03:05:32 +02:00 by Brad Kavanagh · 9 comments

System Information
System: iMac Pro 2017 - MacOS Catalina 10.15.3
CPU: 3.2 GHz 8-Core Intel Xeon W
RAM: 32 GB 2666 MHz DDR4
Operating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro Vega 56 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: blender/blender@375c7dc4ca
Worked: (optional)

Short description of error
I have a scene that's 4000 samples long with various objects and the camera animating almost constantly for a single long shot. The scene is not overly complex with regards to objects, lights and textures. It also seems to render fine and without trouble.

However, upon exporting in any format, once pressing the 'export' button in the export menu the software hangs and my cursor then beachballs.

I've left this for an hour to come back and find nothing has changed. Also tried multiple formats to export to and they're all repsonding the same. Changed location of export, too to an external drive, a NAS or internally and still no change.

MacOS reports the app as unresponsive and the file it's exporting to seems to stay at 0bytes in size.

CPU however is showing to be working heavily for blender in activity monitor [up to 400% CPU thrust there] but disk writing is intermittent and miniscule.

I've screen recorded the process and failure here alongside my activity monitors: F8493502

Exact steps for others to reproduce the error
Open the file, simply head to File > Export... then select Collada [All formats are broken for me, but Collada is what I need for a job due rather soon]. Leave default settings and then click Export.

For me, upon reaching this point, the above description happens.

FILE: MASTER SCENE 1_ANIMATIONS.blend

**System Information** System: iMac Pro 2017 - MacOS Catalina 10.15.3 CPU: 3.2 GHz 8-Core Intel Xeon W RAM: 32 GB 2666 MHz DDR4 Operating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro Vega 56 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `blender/blender@375c7dc4ca` Worked: (optional) **Short description of error** I have a scene that's 4000 samples long with various objects and the camera animating almost constantly for a single long shot. The scene is not overly complex with regards to objects, lights and textures. It also seems to render fine and without trouble. However, upon exporting in any format, once pressing the 'export' button in the export menu the software hangs and my cursor then beachballs. I've left this for an hour to come back and find nothing has changed. Also tried multiple formats to export to and they're all repsonding the same. Changed location of export, too to an external drive, a NAS or internally and still no change. MacOS reports the app as unresponsive and the file it's exporting to seems to stay at 0bytes in size. CPU however is showing to be working heavily for blender in activity monitor [up to 400% CPU thrust there] but disk writing is intermittent and miniscule. I've screen recorded the process and failure here alongside my activity monitors: [F8493502](https://archive.blender.org/developer/F8493502/BLENDER_BUG_EVIDENCE.mov) **Exact steps for others to reproduce the error** Open the file, simply head to File > Export... then select Collada [All formats are broken for me, but Collada is what I need for a job due rather soon]. Leave default settings and then click Export. For me, upon reaching this point, the above description happens. FILE: [MASTER SCENE 1_ANIMATIONS.blend](https://archive.blender.org/developer/F8493465/MASTER_SCENE_1_ANIMATIONS.blend)
Author

Added subscriber: @OMGAlecBaldwin

Added subscriber: @OMGAlecBaldwin
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Did you check Memory usage ? Does it increase or is constant ?
Also in Finder settings, turn off preview using View menu & retry.
Also, use quicktime Player to reduce the resolution of the video, 343 MB being highly wasteful .

Did you check Memory usage ? Does it increase or is constant ? Also in Finder settings, turn off preview using View menu & retry. Also, use quicktime Player to reduce the resolution of the video, 343 MB being highly wasteful .
Member

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

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

Hi Ankit, thanks for getting involved.

Memory usage idles at approx 580MB before export. Once pressing export, usage jumps to approx 650MB and hovered around there until the program is force quitted.

I’ve also turned off preview in finder and executed the export with the same results.

I did originally decrease the size of the video by decreasing the bitrate, but it was almost impossible to see the detail required on the screen to make a thorough follow through. I wanted to ensure anyone watching could see every function and option. I would not consider this ‘highly wasteful’ but appreciate your comment.

Hi Ankit, thanks for getting involved. Memory usage idles at approx 580MB before export. Once pressing export, usage jumps to approx 650MB and hovered around there until the program is force quitted. I’ve also turned off preview in finder and executed the export with the same results. I did originally decrease the size of the video by decreasing the bitrate, but it was almost impossible to see the detail required on the screen to make a thorough follow through. I wanted to ensure anyone watching could see every function and option. I would not consider this ‘highly wasteful’ but appreciate your comment.
Author

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

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

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Member

This report has been classified as a known issue so I'm changing its status to confirmed (Feel free to revert though)

This report has been classified as a known issue so I'm changing its status to confirmed (Feel free to revert though)
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#76083
No description provided.