• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • None
    • 4.2.8
    • Diff
    • None
    • Severity 1 - Critical

      We have a large generated YAML files (40k lines) which will reliably crash sourcetree on diff preview.

      If there are more than a few changes, and the diffs are spread out, memory usage will spiral until it hits 260gb (on my 48gb m3 max) and MacOS kills the process.

      If you ever click on a commit with this kind of change at the top, there is no recovery.

      None of my other git tools, git itself, or any of my IDE embedded tools have this issue, so it's something to do with the diff tool and/or sourcetree's change viewer/component.

            [SRCTREE-8160] Crash on large files with many diffs

            benabee added a comment -

            Hi, I created a project to reproduce the issue. See https://jira.atlassian.com/browse/SRCTREE-8191

            benabee added a comment - Hi, I created a project to reproduce the issue. See https://jira.atlassian.com/browse/SRCTREE-8191

            Andrew added a comment -

            It would be helpful to have the steps to create that crashlog explained.  Perhaps you have a helpdesk article you could share?

            I have sent that crash report to apple dozens of times, so there is something there at least, but that's not what you are asking for I think.

            Andrew added a comment - It would be helpful to have the steps to create that crashlog explained.  Perhaps you have a helpdesk article you could share? I have sent that crash report to apple dozens of times, so there is something there at least, but that's not what you are asking for I think.

            Hi f3d452f22e8d  We tried to reproduce the issue in our environment and not successful so far. Therefore, We request you to kindly share the crashlog and the steps to reproduce the issue. This will give us a better understanding on the issue.

            Arati Mohanty added a comment - Hi f3d452f22e8d   We tried to reproduce the issue in our environment and not successful so far. Therefore, We request you to kindly share the crashlog and the steps to reproduce the issue. This will give us a better understanding on the issue.

              2566180e0bc8 Arati Mohanty
              f3d452f22e8d Andrew
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: