0.42 error after rebuilde

[mikhail73]

At primary generation of a site of an error do not arise

Change detected, rebuilding site
2018-06-12 17:44:46.732 +0300
Source changed "D:\\web\\Hugo\\Sites\\lunacharsky.newgod.su\\content\\pesy\\stihotvornye-perevody.mmark": WRITE
ERROR 2018/06/12 17:44:46 Failed to render "index.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:46 Failed to render "section\\issledovania.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:46 Failed to render "section\\bio.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\tag.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\category.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\author.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\recipient.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\person.html": runtime error: invalid memory address or nil pointer dereference
ERROR 2018/06/12 17:44:49 Failed to render "taxonomy\\series.html": runtime error: invalid memory address or nil pointer dereference
Total in 2756 ms
ERROR 2018/06/12 17:44:49 Failed to rebuild site: logged 9 error(s)

[bep]

It is impossible for me to guess what this is without the source.

[bep]

Possibly related to #4845

[kaushalmodi]

@mikhail73 Do you have disableFastRender set to true? Does the problem go away if you set it to false? Is your answer is yes to both questions, then it's likely that this issue is the same as what bep mentioned above.

[mikhail73]

I have disableFastRender: true

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.