Hi,
I too experienced a problem with the Repo-browser in TortoiseSVN v1.12.0. Downgrading back to v1.11.1 avoids the problem. I'm running on Windows 7 SP1 (64 bit).
The symptoms are a little different in that the Repo-browser window simply closes - there's no crash report, or anything of that nature but the TortoiseProc instance terminates.
I've done a little experimentation. A colleague observed that the issue only occurred on repos where there were externs. I've done a little bit of testing and confirmed that seems to be the case.
I've created a test repo with the following structure:
root
-branches
-BR-test
-tags
-trunk
-test
-vendor
I started to get the problem when I added a repository relative, pegged extern as a property of the trunk/test folder. The extern was "^/vendor@67 vendor". Once commited, any attempt to use the Repo-browser to view the trunk folder (i.e. the folder *above* the one with the defined extern) by selecting it in the outline view, causes the TortoiseProc instance to terminate within less than 1 second (i.e. not quite immediately).
The issue occurs if I simply start the Repo-browser generally and navigate to the trunk folder. It also occurs if the Repo-browser is initiated from another dialog (e.g. the Merge dialog). For example, the following steps trigger the issue:
- Checkout the BR-test branch
- Right click the root of the checkout and, from the context menu, select the ToroiseSVN -> Merge... menu item
- In the merge dialog, select "Merge a range of revision" as the merge type and click the Next button
- For the next page, with the "URL to merge from" set to "[my protocol, server, and repo]/branches/BR-test" click the ellipsis button to initiate the Repo-browser
- In the Repo-browser, select the trunk folder from the outline view
- The Repo-browser and the Merge dialog close and TortoiseProc.exe is no longer shown as a process in the Windows Task Manager
I ran these tests on a VM and can confirm that the VM running v1.12.0 exhibits the problem while my base PC running v1.11.1 does not have the issue, when viewing the same repo.
I hope these details help with the investigation.
Regards.