NOTE: when using --enable-logging on the command line, config options are not loaded. Not sure why, or how many options are ignored but it prevents the logging of the error. Upon reloading, resetting the option to cause the problem, then running from the commandline again with logging enabled, the fault recurred, and the logfile was generated but empty.
If you need anymore information, feel free to ask.
This is probably due to an interaction with the "Open new tabs next to the current one" setting. Which could cause a crash on startup in past versions, but has since been fixed.