Issue #2587 resolved

2.8 crash on push/pull to/from remote repository.

Jay Lonnquist
created an issue

Windows Vista 32bit. While attempting to push or pull to/from remote repository via workbench or directly from sync, application crashes.

Downgrading to 2.7.2 resolves the issue.

I've attached information from Windows Event Viewer. Apologies to those unable to read Japanese, but that's the locality I'm working from these days:

Also attached Event Viewer generated xml.

障害が発生しているアプリケーション thgw.exe、バージョン、タイム スタンプ 0x4f3f0f2f、障害が発生しているモジュール ntdll.dll、バージョン 6.0.6002.18541、タイム スタンプ 0x4ec3e3d5、例外コード 0xc0000374、障害オフセット 0x000b06b7、 プロセス ID 0x1dc、アプリケーションの開始時刻 0x01ce4b8a20db3115。

Comments (11)

  1. Yuya Nishihara

    Could you try to disable mercurial_keyring extension, which is enabled since 2.8 ?

    1. open "TortoiseHg Settings" dialog and click "Edit File"
    2. add the following lines to [extensions] section
    mercurial_keyring = !

    or remove mercurial_keyring = from C:\Program Files\TortoiseHg\hgrc.d\Mercurial.rc.

    1690 says thg+mercurial_keyring crashes with the exception code 0xc0000374, but I couldn't reproduce it.

  2. Ian Kemp

    I had the exact same issue after upgrading to 2.8.0, but a different stack trace:

    Faulting application name: thg.exe, version:, time stamp: 0x4f3f0f36
    Faulting module name: QtCore4.dll, version:, time stamp: 0x50be0bf9
    Exception code: 0xc0000005
    Fault offset: 0x0000000000027e0e
    Faulting process id: 0x2ccc
    Faulting application start time: 0x01ce4c07d36aeac6
    Faulting application path: C:\Program Files\TortoiseHg\thg.exe
    Faulting module path: C:\Program Files\TortoiseHg\QtCore4.dll

    Disabling mercurial_keyring in Mercurial.rc seems to have resolved the error for me.

  3. Ian Kemp

    Can we maybe get a new build of THG (2.8.1?) that disables mercurial_keyring by default, or perhaps a notice on the homepage advising users to disable mercurial_keyring if they experience crashes with THG 2.8?

  4. Marcus M.

    Could somebody that had the issue before try to reproduce the issue with a current release? I think enabling keyring by default is ultimately a user-friendly decision and should be attempted again, if possible.

  5. Log in to comment