nemo crashed with SIGSEGV in g_closure_invoke() when opening new tab

[svdbeek]

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

nemo:
  Installed: 2.8.6-2
  Candidate: 2.8.6-2
  Version table:
 *** 2.8.6-2 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

Action: Open a New Tab once nemo was opened
Expected result: nemo opens a New Tab page
Actual result: nemo crashed and disappeared from the screen

I was able to reproduce the bug several times, as follows:
1) Open nemo
2) Navigate away from the default directory it opens in ($HOME in my case)
3) Open a new tab -> Crash

This worked several times in a row - it doesn't always crash the first time, but always seems to crash after 2 tries, if it doesn't crash after 1.
Opening a new tab IN the default location will also crash the application, but not as frequently.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nemo 2.8.6-2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Apr 9 14:23:32 2016
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2013-04-19 (1085 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: nemo
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
Signal: 11
SourcePackage: nemo
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nemo crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip input libvirtd lpadmin plugdev sambashare sudo vboxusers www-data

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545800, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Paul Smith (pjsanfil)]

In order to recreate this bug I had to do the following:
1. Open nemo
2. Navigate away from the default location, for example to $HOME/Pictures
3. Open a new tab
4. Close the new tab
5. Open a new tab again

I noticed some directories seem to never cause this problem if the directory name is short. For example $HOME/help does not cause the crash.

Just wondering, how are we supposed to comment on this bug if we aren't supposed to comment here but we cannot see the private bug to comment on that?