P4 Merge Crashing

Hi AnswerHub!

So, my UE crashes when I try to use p4 as source control for files. used to work fine til I updated both the P4 client and 4.6.1 (can’t figure out which did it, but i cannot seem to get around it.

Any ideas what could this be?

When does your editor crash? On startup or on connection to source control? Do you have a log file that you could post here?

When i go to ‘editor preferences/ Leading & Saving/ Source Control’, It all goes fine. Then i check ‘Use Glogal settings’ and the window with the connection settings pops up but immediately UE crashes.

Also, if I just go through File/ Submit to Source Control’ same thing happens.
I submitted a crash report last night.

Do you have a log file that shows what you were doing when the crash occurred? Log files are in [PROJECTDIR]/Saved/Logs.

Hi, So,I just created a brand new project, chose to connect and crashed. latest version of Perforce and using UE4.6.1

How should i post the file? For now on dropbox

It’s odd, just did same test on different pc and same result: new project, connect to source control, crash

reverted to previous working p4v, still crahing.

Reverted also to 4.5 and still crashing. What is odd is that it’s happening on 2 different computers. My “coworker” has the same versions i had earlier and can still connect and submit to my P4 server…

Thanks for posting your logs, it gets us a little closer to the problem!

The crash isn’t occurring inside the editor, rather it is failing with a stack overflow inside the windows networking system. Something inside ASProxy64.dll or WS2_32.dll is trying to allocate something large on the stack.

Very odd, as you say - as the crash looks like it may have something to do with your windows configuration it is strange that it would occur on two machines. I will try to unearth your crash report form our DB when it is back up (it is not working at present) and gather more information.

Our crash reporter DB is now back up but is missing a few days worth of reports. Once these are back in place I will take another look to see if yours is there.

Unfortunately I have not been able to retrieve the crash report shown above - it never ended up in our DB. The last thing I can suggest to help us diagnose your issue is to enable verbose logging before you enable source control in the editor. Open a console (‘~’ key usually) and type:

Log LogSourceControl verbose

If you then try to connect (and crash), the logs should contain some more information that could help us track the issue down. If you post them here that would be really helpful.

Hi Tom,
Thanks for your help. Unfortunately i have still not been able to resolve the issue. I tried uninstall/ reinstall with no success. I followed your suggestion and got the log after the crash. I also submitted the report with the description “Perforce crash”.

I hope we can figure this out. we are desperate!

It gets strange… I was thinking there might be something wrong with compatibility on the server or maybe some perforce aspect but i installed p4 and ue4 on 2 remote pc’s and they both work under my same server. only the 2 pc’s inside the lan (one of which is the server) crash. Please help!

We have found that the crash reports submitted to our DB did get through, but our system was unable to resolve the callstack’s symbols, so we cannot get any more information from them. Have you built your own editor from source?

I now finally have found your crash report and analyzed it, but unfortunately the dump does not include a valid callstack for the worker thread in question (probably because the stack is trashed by the stack overflow). I’m continuing investigations, but its not looking hopeful.

As we cannot reproduce the issue here, my only suggestion now would be to locally build the editor and attempt to reproduce the crash yourself. Hopefully this will yield a valid callstack that we can use to further investigate.

i don’t even know what that means =(
Sorry. I have not built my own editor, i literally just updated and it somehow broke. I will try again to uninstall/ reinstall everything… It’s very strange that it broke on 2 pc’s but continues to work on 2 others using the same server and versions of both software packages.

I will report back if anything happens.

Hey, i may be getting closer to something, but im not sure… I just realized a common thing with both pc’s is that when the source control screen shows up, the username for perforce is wrong, making it crash.

I uninstalled p4 and I ran source control in ue4 and it ran fine (no crash, except it couldn’t connect to p4). When i reinstalled it, it automatically set the username as the pc’s name and not what was specified before, giving me an error to connect. I set the username as it’s supposed to be and connected perfectly.

Ran Source control in UE4 and it was still showing as the pc’s name and not the username, giving me a crash.

Now i need to find where to change the default username for p4 connection in ue4… any idea how i may do this??

We try to autodetect the connection from the current environment settings. You can set these in P4V under the “Connection->Environment Settings…” menu.

After breaking my head with a group of people, none of which could figure this out, i decided to format my pc and reinstal windows (that desperate).

Did the updates, installed p4, installed UE4-- WORKS!!.. but now i was curious as to what was causing the crash… so i went down the list of tools and software i had installed on my pc and finally found the culprit – ASTRILL VPN!!! – i had it installed on both computers where UE was crashing.

Installed Astrill, crash… uninstalled… worked again!

It didn’t matter wether i had it on or off, just the fact it was installed was enough for the crash.

Is there a way I can fix this? (being able to have astrill on my pc and use UE4??)

Perhaps you could contact Astrill for any tips on how to avoid this? They are likely hooking into some low-level windows systems. I will log an issue our side to track this!