崩溃¶
引起Blender崩溃的最常见原因:
运行内存不足。
图形硬件或驱动程序的问题。
Blender里的bug。
首先，你可以通过 来恢复你的工作。
To prevent the problem from happening again, you can check that the graphics drivers are up to date (图形硬件), upgrade your machine's hardware (the RAM or graphics card), and disable some options that are more memory intensive:
减少撤消次数 。
使用多重采样抗锯齿也会增加内存使用量并使显示速度变慢。
On Linux, the Window Manager (KDE and Gnome for example) may be using hardware accelerated effects (e.g. window shadows and transparency) that are using up the memory that Blender needs. Try disabling the desktop effects or switch to a lightweight Window Manager.
To check memory usage by Blender:
On Windows, use Task Manager and sort by Memory.
On macOS, use Activity Monitor.app and open Memory tab. Alternatively, run
top -o MEM.On Linux, run
top -o %MEM.
崩溃日志¶
When Blender crashes, it writes out a text file which contains information that may help identify the cause of the crash. Usually, this file is written in the 临时目录 directory.
This file contains a log of tools used up until the crash as well as some other debug information. When reporting bugs about crashes it can be helpful to attach this file to your reports, especially when others are unable to reproduce the crash.
Windows¶
On a crash, a file is written based on the name of the currently loaded blend-file,
so test.blend will create a file called test.crash.txt.
Batch scripts are provided in Blender installation directory which may be run to obtain the Blender debug log and system info text files:
blender_debug_log.cmdis used in most cases.blender_debug_gpu.cmdandblender_debug_gpu_workaround.cmdlog GPU-related errors.blender_factory_startup.cmdstarts Blender with default settings which is recommended for debugging.
If the crash happens in Blender module, stack trace is also written to a file named blender.crash.txt.
The path to that file can be found at the end of blender_debug_log.txt file.
macOS¶
After crash, macOS Crash Reporter shows a window after some time, or next time Blender is opened. Copy the text in the crash report and save it in a text file. That file should be attached to the bug report.