Page MenuHome

Silently crashing when a file can't be written in a jiffy
Closed, ResolvedPublic

Description

System Information
Windows with external portable hard drive (NTFS)

Blender Version
Broken: 2.68 on up

Short description of error
Drive takes a nap, Blender tries to save a frame, Blender disappears. Seems to be that Blender can't deal with any kind of drive latency, and furthermore when Blender can't write a file, it just dies.

Exact steps for others to reproduce the error

  1. Set Blender up to render a really hefty frame sequence (like 2 minutes per frame).
  2. Specify your portable drive with safety-locking mechanism as output destination.
  3. Watch as Blender refuses to wait 5 seconds for the drive to wake up and opts to kill itself instead. This may happen at any time, especially when you are doing other things in the background that cause the render to take longer (giving the drive time to fall asleep). I have not seen any error message when Blender crashes while failing to write a file. It should also be noted that the file usually seems to get written after all, but when Blender goes to check if it exists (I'm guessing that's what's happening) it crashes. The drive in question is capable of caching files in a solid state chip before writing them, so they likely don't touch the disk until after Blender crashes.

Details

Type
Bug

Event Timeline

Fluffy Rabbit (fluffrabbit) created this task.
Fluffy Rabbit (fluffrabbit) raised the priority of this task from to Needs Triage by Developer.

Can you upload a test file which crashes on animation render?

Campbell Barton (campbellbarton) triaged this task as Needs Information from User priority.May 8 2014, 11:59 PM

Note, I tried to redo this bug on Linux

  • rendering to a mounted FTP site, via curlftpfs
  • rendering with simulated disk errors with fiu-run

And couldn't get any crashes while rendering an animation, so perhaps this is a windows-only problem.

@Fluffy Rabbit (fluffrabbit)

Could you try the following.

  • Run blender from a terminal, (cmd.exe) and see if any messages are printed on crashing.
  • Try some alternative slow media, like a very slow network filesystem (mounted FTP or similar).

I looked into simulating slow disk performance in windows but couldn't find good tools for that.

Well, shit. I can't reproduce this bug in 2.70a. I don't know what that means.

closing, we can reopen if you manage to redo on a recent build.

please always try a recent build before reporting bugs, it saves us time.