Page MenuHome

Add debug logging info to crash docs

Authored by Ankit Meel (ankitm) on Sep 4 2020, 4:59 PM.



Often times on the bug tracker, this info is repeated.
It should be good to have it in the manual.

Diff Detail

rBM Blender Manual

Event Timeline

Ankit Meel (ankitm) requested review of this revision.Sep 4 2020, 4:59 PM
Ankit Meel (ankitm) created this revision.

Here are some technicalities.

Often times on the bug tracker, this info is repeated.

Yes, I think, that requesting short list of actions is quite effective. Just pointing user to document like this would probably result in him doing half of things I wanted. With short list I can check if everything that was requested was also done.
So I wouldn't see document like this as something that I would point user to while requesting logs, but rather a resource for user that say: "I didn't understand a word that you said". I haven't got much problems when requesting logs though.

Also we have button on phabricator for common responses. Even though some I type faster on keyboard nowdays... I use it mainly for links, but that's besides the point.


test.blend will create a file called test.crash.txt. Is quite important information IMO


However, if autosave preferences is enabled, this script may override them.

Isn't autosave prefs a preference? So what happens is actually known. Also to me this sounds like a bug - I wouldn't expect loading factory settings to overwrite preferences unless I click on save preferences button.


On Blender 2.91+

I guess it is irrelevant to state blender version. Manual is expected to be correct for "current" version

if the reason of crash is `EXCEPTION_ACCESS_VIOLATION`

It that true? and is that even important information?

Ankit Meel (ankitm) marked 2 inline comments as done.

review update: remove blender version, remove exception name, fix text about autosave, add link to GPU index.


Auto-save is enabled by default as of now. So changing preferences in factory startup mode and quitting Blender will override the settings.


I will accept as in I am not against :)


I just tried: Run blender_factory_startup.cmd, change Resolution Scale to 2, quit Blender.
This setting wasn't saved. Same happens if I save .blend file. I am not exactly sure how it should work though.

This revision is now accepted and ready to land.Sep 7 2020, 7:16 AM

Remove comment about factory startup overriding settings.

This revision was automatically updated to reflect the committed changes.