Lobby Appcrash after login

This is for troubleshooting of problems with the FAF client and Forged Alliance game.

Moderator: PhilipJFry

Lobby Appcrash after login

Postby d-_-b » 08 Sep 2015, 21:01

Crash Window:

Code: Select all
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   FAForever.exe
  Application Version:   0.10.125.0
  Application Timestamp:   49180193
  Fault Module Name:   QtGui4.dll
  Fault Module Version:   4.8.6.0
  Fault Module Timestamp:   53af0542
  Exception Code:   c0000005
  Exception Offset:   0016fbe0
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   2057
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789


It happened after a game, ie: client loaded fine, played a game, finished the game and found the fa client would not maximise (it viewed only as a titlebar), so i closed it and reopened it. This issue now started and has persisted since.

have tried a clean faf reinstall, no change.

unlike last time i had a similar issue, where downlords client did NOT WORK, and fixing the issue for that also fixed the regular faf client, so i went back to using it.
Attachments
uid.log
(312 Bytes) Downloaded 20 times
forever.log
(2.63 KiB) Downloaded 22 times
User avatar
d-_-b
Avatar-of-War
 
Posts: 93
Joined: 19 Jun 2015, 01:58
Has liked: 6 times
Been liked: 20 times
FAF User Name: d-_-b

Re: Lobby Appcrash after login

Postby d-_-b » 13 Sep 2015, 05:13

last time i had this issue, it was from an incompatable DLL version of some linked lib this is using in my system32 folder. It also affected downlord's client in the same way, who'se detailed exceptions led to the root of the issue. However, downlord's works fine, so i doubt this is the issue this time...

i have tried starting faf from a command prompt with the PATH variable set to only "./" so it should only load DLLs from the folder it is in. still same issue.

As you can see, the logs really dont show anything useful. No idea where the program is crashing.
Is there a way i could run this in the python interpreter directly and find out the exact line the crash occurs on?

if so could i pull the source from github and just run it in the interpreter?

running downlord's client is a dirty temporary way to keep playing, its getting quite good, but there are yet unimplemented features, as i can't update mods (im given to understand the way this works will change soon), when the game is updated i will no longer be able to play. Beta already desyncs me.
User avatar
d-_-b
Avatar-of-War
 
Posts: 93
Joined: 19 Jun 2015, 01:58
Has liked: 6 times
Been liked: 20 times
FAF User Name: d-_-b


Return to Tech Support

Who is online

Users browsing this forum: No registered users and 1 guest