• Type: Bug
• Resolution: Duplicate
• Priority: Low
• Fix Version/s: None
• Affects Version/s: None
• Component/s: None
• Labels:

  • crash

1. sourcetree_dwhite.log

   8 kB

   15/Mar/2016 2:35 PM

2. sourcetree.log

   111 kB

   29/Feb/2016 9:23 AM

[SRCTREEWIN-5031] Crash on submodule handling

Collapse comment: minnsey added a comment - 13/Apr/2016 5:27 AM

minnsey added a comment - 13/Apr/2016 5:27 AM

Hi

Thanks for reporting the issue, we have a fix being released shortly. Please follow the duplicate link,

Expand comment: minnsey added a comment - 13/Apr/2016 5:27 AM

minnsey added a comment - 13/Apr/2016 5:27 AM Hi Thanks for reporting the issue, we have a fix being released shortly. Please follow the duplicate link,

Collapse comment: David White added a comment - 15/Mar/2016 2:32 PM, Edited by David White - 15/Mar/2016 2:36 PM

David White added a comment - 15/Mar/2016 2:32 PM - edited

I had the same problem. I'm using SourceTree 1.8.2.11.

In my case I had a repo with one submodule. I committed a change in the submodule then made another change in the submodule that I did not check in.

In the parent repo, I committed the submodule update. It went to the "Submodule Check" dialog where it found the uncommitted change in the submodule. I clicked "Open," and it crashed.

I've attached the end of my sourcetree log as "sourcetree_dwhite.log"

Expand comment: David White added a comment - 15/Mar/2016 2:32 PM, Edited by David White - 15/Mar/2016 2:36 PM

David White added a comment - 15/Mar/2016 2:32 PM - edited I had the same problem. I'm using SourceTree 1.8.2.11. In my case I had a repo with one submodule. I committed a change in the submodule then made another change in the submodule that I did not check in. In the parent repo, I committed the submodule update. It went to the "Submodule Check" dialog where it found the uncommitted change in the submodule. I clicked "Open," and it crashed. I've attached the end of my sourcetree log as "sourcetree_dwhite.log"