There is a dependency cycle currently: Contents -> Navigation -> Orchard.ContentPicker -> Contents

If a new migration becomes necessary on a feature that depends on one of those, a stack overflow stops the server before it even has a start to log anything.

The dependency should be broken, for example by moving the content menu item that requires ContentPicker to a separate feature.