Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-13209

Huge diff loading shouldn't lock Sourcetree

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • General
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Environment

      • Windows 7 Professional 64-bit
        • Outdated, I know
      • Sourcetree v3.3.8.3848

      Steps to Reproduce

      1. Commit a text file
      2. Write a huge amount of lines (e.g. 20,000 lines) to the file
      3. Add and commit the change
      4. Show "History" page

      Current Behavior

      • Sourcetree tries to display the huge diff fully, and a user can't do anything but just wait for a long time or terminate this app because it never releases the whole control before finishing everything

      Appreciated Behavior

      Any one (or more) of these:

      • Sourcetree tries to display the huge diff fully, but a timeout occurs because it took too long time to load
        • It would be great if the timeout length can be modified in preferences.
      • Sourcetree tries to display the huge diff fully, but a user can interrupt it anytime by pressing Esc key or a kind of "Cancel" button
      • Sourcetree tries to display the huge diff fully, but a user can interrupt it anytime by clicking on another file or commit with light changes because loading is processed only in the diff pane at the lower right
      • Sourcetree displays diffs partly only within the scrolled area of the diff pane
      • Sourcetree doesn't start to display diffs automatically before selecting a file in commits
        • It's just like the diff pane of the "File Status" page says "Select a file to view the diff" when no files are selected.
      • Sourcetree doesn't start to display the huge diff automatically because this app knows its hugeness before the loading
        • It's just like GitHab says "Large diffs are not rendered by default" when showing commit detail page.
      • Or another cool solution...

      Attachments

        Activity

          People

            Unassigned Unassigned
            9af9e1c2cccd 森の子リスのミーコの大冒険
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: