x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Unreal 4.12 and 4.12.1 crash when perforce is selected in "Connect to source control"

Unreal 4.12 and 4.12.1 is crashing when perforce is selected in "Connect to source control". I receive this message after the crash in the crash reporter: "You do not have any debugging symbols required to display the callstack for this crash."

Product Version: UE 4.12
Tags:
more ▼

asked Jun 08 '16 at 08:56 AM in Bug Reports

avatar image

Nesvi
3 2 4

avatar image Doug E ♦♦ STAFF Jun 08 '16 at 02:17 PM

Hey Nesvi-

When you received the crash report window, did you press the submit button to submit the crash? If so, can you provide your machine Id to help me look up your crash? When I create a new project and select Source Control->Connect to Source Control and select Perforce as the Provider I am not getting any crash. Can you confirm if these are the same steps you're using and if you see the crash occur in a new project? Can you provide the logs from the crash as well?

avatar image Nesvi Jun 09 '16 at 08:28 AM

Of course. This is all the output I have.

MachineId:D986BBDB460C5967FA45A0AAB63D6D48 EpicAccountId:15536383c82e490cb5a5eeaba9a5bc87

You do not have any debugging symbols required to display the callstack for this crash.

avatar image Doug E ♦♦ STAFF Jun 09 '16 at 12:49 PM

Unfortunately the crash report does not contain as much useful information in this case. If you are using the launcher, can you click the dropdown next to Launch for the engine version and select Options. Please check that "Editor symbols for debugging" is checked which should provide you additional information after a crash. Also, please let me know if the following steps cause the crash to occur for you.

  • Create a new project in 4.12

  • Click Source Control->Connect to Source Control

  • In the new window select Perforce as the Provider

If this does cause you to crash, let me know if adding editor symbols provides any additional information in the callstack window. Also please add the log files from the crash.

avatar image Nesvi Jun 13 '16 at 08:09 AM

Hi,

That caused me a crash. Here is the information with the editor symbols. Thanks for your help.

 MachineId:D986BBDB460C5967FA45A0AAB63D6D48
 EpicAccountId:15536383c82e490cb5a5eeaba9a5bc87
 
 Stack overflow - code c00000fd (first/second chance not available)
 
 LavasoftTcpService64
 LavasoftTcpService64
 ws2_32
 UE4Editor_PerforceSourceControl!NetTcpSelector::Select()
 UE4Editor_PerforceSourceControl!NetTcpTransport::SendOrReceive()
 UE4Editor_PerforceSourceControl!NetBuffer::Receive()
 UE4Editor_PerforceSourceControl!RpcTransport::Receive()
 UE4Editor_PerforceSourceControl!Rpc::DispatchOne()
 UE4Editor_PerforceSourceControl!Rpc::Dispatch()
 UE4Editor_PerforceSourceControl!Rpc::Dispatch()
 UE4Editor_PerforceSourceControl!Client::WaitTag()
 UE4Editor_PerforceSourceControl!Client::RunTag()
 UE4Editor_PerforceSourceControl!Client::Run()
 UE4Editor_PerforceSourceControl!ClientApi::Run()
 UE4Editor_PerforceSourceControl!FPerforceConnection::RunCommand()
 UE4Editor_PerforceSourceControl!FPerforceConnection::EstablishConnection()
 UE4Editor_PerforceSourceControl!FPerforceConnection::FPerforceConnection()
 UE4Editor_PerforceSourceControl!FScopedPerforceConnection::Initialize()
 UE4Editor_PerforceSourceControl!FPerforceGetWorkspacesWorker::Execute()
 UE4Editor_PerforceSourceControl!FPerforceSourceControlCommand::DoThreadedWork()
 UE4Editor_Core!FQueuedThread::Run() [d:\build\++ue4+release-4.12+compile\sync\engine\source\runtime\core\private\hal\threadingbase.cpp:430]
 UE4Editor_Core!FRunnableThreadWin::Run() [d:\build\++ue4+release-4.12+compile\sync\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:74]

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hey Nesvi-

I've entered a bug report for this crash, UE-31953 . To add additional information to the report, could you provide your DXDiag as well as the logs from the crash?

Cheers

Doug Wilson

more ▼

answered Jun 13 '16 at 04:07 PM

avatar image Nesvi Jun 14 '16 at 10:33 AM

[link text]Here is the dxdiag.[1] Thanks for your help.

[1]: /storage/temp/94579-dxdiag.txt

dxdiag.txt (90.8 kB)
(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question