I don't know how to launch Blender from "the command line". Perhaps, we should wait for any other Windows users ?

Another Windows user can confirm this please ?

No crash here, Win7 gtx 550ti in latest Master and the release 2.79

I can't reproduce either, maybe attach a .blend file? There could be some different default settings in your startup.blend.

I let you a simple file I created with a plane. On my computer, just going on Rendered mode makes Blender closing after 1 second of render. I also tried with the blender-2.79-42a5624-win64 build of yesterday. I doesn't crash if no geometry is there.

cannot reproduce either (both rendered viewport and F12 work fine here)

F12 works well for me too, it's only Rendered mode that makes Blender crash.

I still can't reproduce the crash with the attach .blend file, on Windows 10. I tried checking with valgrind but it didn't reveal any issues.

Does it crash every time, or only randomly some of the time? Did you try loading factory settings and then loading the freestyle_crash.blend, to see if perhaps any addons or other user preferences might be causing this?

It crashes all the time. I renamed the 2.79 folder in C:\Users\Owners\AppData\Roaming\Blender Foundation\Blender so Blender starts without my usual addons and preferences and it works so you're right it comes from this. Do you have a clue where to looking for or there are too many parameters to guess what kind of addon could interfere with freestyle rendered mode ?

Well, I found it faster than I thought. I guessed that it was a Community addon and something that appeared in 3D view and so, by deactivating Animation : Timecode (https://github.com/RayMairlot/Timecode), it works.

The problem here is that Freestyle is changing the frame during viewport render, which should not happen but Freestyle does it anyway.

If it's complicated to fix I might just close this report though, since Blender Internal is being removed.

@Brecht Van Lommel (brecht) : I think we can close this then?