Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #1860
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Racecondition in git.exe Progress Dialog

By costin.l... on August 20, 2013 20:37 (imported from Google Code)


Not consistent but here it is.
What steps will reproduce the problem?

  1. Use /closeonend (1,2,3 all behave the same). For example
    C:\Program Files\TortoiseGit\bin\TortoiseGitProc.exe /command:commit /path:[..] /closeonend:2

  2. commit something to the repo repeatedly potentially by pressing a key right after commit has started

  3. I get an error message saying SendRpt: Error - no dump was created

What is the expected output? What do you see instead?

The commit is successful yet tgit informs me that something went wrong. My assumption is that the closeonend causes some race condition (exhibited when pressing a key during the closing process) which triggers the false positive - in this case the incorrect error message.

I couldn't find a way to reproduce this 100% but it's quite annoying as it occurs every 3-5 commits.

What version of TortoiseGit and msysgit are you using? On
what operating system?

Latest - TGit 1.8.5 with git 1.7.11. The same issue appeared on 1.8.4.

Please provide any additional information below.
I'm upgrading from tgit 1.7.15

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking