4.9.0 hangs forever on Mac with svn with "Updating file(s) source control status..."

Development Pipeline & Plugins
, , , , , ,
1

I’m using subversion for source control on a Mac.

Every once in awhile clicking the “Save” button from any window (or trying to quit the editor) (or trying to check in to source control) will pop up a dialog saying Updating file(s) source control status… – and nothing ever happens. The editor UI is frozen. Selecting main menu items from the app-level menu does nothing. I have to force quit the editor.

Very, very, very annoying. It’s like a special constant crashiness just for me. :frowning:

Since I have Xcode installed, and 4.9.0 uses the system subversion on Mac when present, here’s the system svn info:

$ svn --version
svn, version 1.7.19 (r1643991)
   compiled Jun 17 2015, 13:48:11

Copyright (C) 2014 The Apache Software Foundation.
This software consists of contributions made by many people; see the NOTICE
file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme

Some background:

Since UE4 ships with svn 1.8.x, and I had been using svn 1.8 installed by homebrew previously to do the initial svn checkout, the svn 1.7 client wouldn’t even work due to incompatibilities between the versions. So, inconveniently, I uninstalled the homebrew-installed subversion and checked out a new copy using the system svn. (On the flip-side, not having to manually run the UE4-included svn binary from the shell after each point update to re-cache my svn password will be a welcome change). After I did all that, I could launch the editor and source control would connect. But then the hang occurs eventually. I was able to go about 2 hours without it happening once. More often it happens about every 20-30 minutes.

2

Hello ,

Thank you for reporting this issue. I’m looking into this issue and I haven’t been able to repro the issue so far. I’ll be looking into it further but any additional information you can provide would be helpful in the meantime.

3

The subversion repository is served from a CentOS 7.1 server running subversion 1.7.14

$ svn --version
svn, version 1.7.14 (r1542130)
   compiled Feb 10 2015, 23:03:21

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people; see the NOTICE
file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme

The subversion repository is being served up via svnserve via the command:

svnserve --config-file svnserve.conf --root /home/svn -d

The config file svnserve.conf looks something like this:

[general]
anon-access = none
auth-access = write
password-db = passwd
realm = My Company

The password file passwd looks something like this:

[users]
myuser = mypassword

The resulting URL is on a custom port (specified in the conf file), and looks like this:

svn://example.com:7890/reponame

After having manually got the appropriate files and directories into the repository by following the (very shaky and incomplete) UE4 docs, users on OS X Yosemite 10.10.5 check it out with a command like this:

svn checkout  svn://example.com:7890/reponame

My project was created under UE4.7.x, upgraded to 4.8.x and then put into subversion which worked…sorta okayish. Didn’t freeze at least. Upgraded to 4.9.0 and now I can barely work at all without this freezing up the engine. I spent a quarter of my last work shift just force-quitting the application and restarting it and trying to something that wouldn’t cause a freeze.

@ If I understand correctly that you are an Epic Games employee, I can provide you with an actual login to the actual repo via some non-public means and you can try it yourself. I currently have a set of simple steps that causes the freeze in about 15 seconds at will with this project. (Because it’s what I’m trying to change that causes the freeze)

4

For now, I have disabled source control entirely. Source control with UE4 has been a joke no matter what settings I have tried.

5

Hello ,

You’re correct, I am an Epic Games employee. It would be very helpful to have that login / repro case. If you would like to send this information privately, you can send me a private message on the forums. Here is a link to my [profile][1].

While this information will be private, there will be at least one other person using the login provided as someone else inside the company will be helping with this issue.

6

I sent you a PM last night with all the info.

7

Hello ,

We’re still looking into this issue and will let you know if there are any updates or if we need any further information. Speaking of which, would it be possible for you to provide your logs from the editor after running into the issue in the meantime?

8

Hi ,

Thank you for your patience and for setting up access to your subversion repository for us. I’ve placed a bug report into our system for the issue. For your reference, the bug number is UE-21584. Please note that the repository that you provided is crucial to the reproduction of this issue, meaning it is very helpful if you can keep the repository in it’s current state. I’ll be sure to update you here when we’ve made progress on the issue.

9

Oh, good! I’m fine leaving the repository for the time being.

Sorry I haven’t been able to get you the logs, I’ve been in “crunch time”, so life has been crazy. Do you still need the logs, or do you have a good handle on it? I can try to get you them tonight if you still need them.

10

Any additional information would be helpful. I can add the logs to the bug report if you have time to provide them.

11

I hope this is the log file you were looking for.

link text

12

Does the fact that this “answer has been accepted” (according to the email I received) mean that the bug has also been fixed? Is there a way for me to view bug UE-21584, by the way? Or is that on an internal system?

13

The resolved status is for tracking purposes and means that the bug has been entered. The bug number is not something you can do anything with personally as it is on an internal system, but I gave it to you so that if you ever need to ask about its progress that the person helping you can look it up quickly.

14

Okay, thanks for clarifying that.

15

I have the same issue with a repository of mine.
The issue has been present since UE4.8

Is there any more information about it?

16

Hello daniele_niero,

The issue is in the process of being worked on but unfortunately I have no estimate as for when it will be fixed.

17

Thanks.

Have you seen my answers on this other discussion? (still about the same issue)