These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
Previous page123
 

Client freezes and symbolic links

First post
Author
Previous Topic Next Topic
Ransu Asanari
Perkone
Caldari State
#41 - 2013-12-14 05:21:20 UTC
For anyone else interested, here is the original thread I created about client freezes with some extra detail:

https://forums.eveonline.com/default.aspx?g=posts&m=3874027
CCP Snorlax
C C P
C C P Alliance
#42 - 2013-12-14 11:22:43 UTC
I did fix the audio related freeze when docking/undocking earlier this week. I have that confirmed from one player who consistently froze on undock when audio was enabled. Of course it is possible there are further issues related to audio, but if you've had problems with that in the past, please try re-enabling audio (I'd suggest undocking somewhere safe first!).

CCP Snorlax - Software Architect - Team RnB - @CCP_Snorlax - http://ccpsnorlax.blogspot.is/
Vincent Athena
Photosynth
#43 - 2013-12-15 05:31:14 UTC
CCP Snorlax wrote:
Vincent Athena wrote:
I got a log from a client that experienced a freeze. This was on an alt account. The log was made from the monitor window. Unfortunately, there was no crash log or python trace file as the client never crashed, but got frozen. (Actually there was a crash log file, but it is zero bytes long and empty).

I had three clients running during a mining op, 2 hulks and an orca. The client running the orca froze right after I had it warp to station. Just before the freeze the client displayed an exception. Getting an exception message displayed before the freeze is actually rare, and this may not be the actual "Mac freeze bug". But it is a bug with a freeze.

Bug report filed with "CCP Snorlax" in the title. Hope this helps.

Thanks for the report. The logs in this case indicate the process ran out of memory. That is probably the reason there is no dump.

I need to investigate further if any of the warning preceding this could explain why the memory runs out - there must be a memory leak somewhere.

Ive been doing more sessions with monitor logging running. I set the monitor to the memory tab to see if there was anything to see. With logging turned on the green line showing python memory slowly crept up. Total memory went up with it. Eventually the client got slower and slower, then crashed. It took about 2 hours. Turning logging off stops the slow creep.

When I had logging turned on I also had it saving to file.

So apparently the logging process itself crashes the client.

Know a Frozen fan? Check this out

Frozen fanfiction
CCP Snorlax
C C P
C C P Alliance
#44 - 2013-12-15 09:26:01 UTC
Vincent Athena wrote:

Ive been doing more sessions with monitor logging running. I set the monitor to the memory tab to see if there was anything to see. With logging turned on the green line showing python memory slowly crept up. Total memory went up with it. Eventually the client got slower and slower, then crashed. It took about 2 hours. Turning logging off stops the slow creep.

When I had logging turned on I also had it saving to file.

So apparently the logging process itself crashes the client.

Sigh. This is one more reason for me to overhaul the logging system (luckily it's already high on my list).

CCP Snorlax - Software Architect - Team RnB - @CCP_Snorlax - http://ccpsnorlax.blogspot.is/
Vincent Athena
Photosynth
#45 - 2013-12-15 15:23:55 UTC
On the bright side the classic Mac freeze has not happened to me in quite awhile. The bug I reported to you was not the classic freeze as I got an exception notice first. And that one now appears to have been caused by the logging process. The classic freeze; the client just stops.

Ill keep logging and await issues.

Know a Frozen fan? Check this out

Frozen fanfiction
Giorgos Rbs
Lead Head Inc
#46 - 2013-12-27 23:09:13 UTC
I haven't read in detail all replies to this thread but I saw no solution posted. I will just describe what happens to me since the thread looks relevant.

I always play windowed mode, and sometimes will run up to 4 clients (usually 2). I have an OK PC at home (i7, GTX660, 12gb ram) and a laptop (i5, Georce GT525M. 4gb ram) that can barely run the 4 windowed eve. Both systems run Win 7 x64.

After Rubicon was deployed both computers started having the same issue. EVE freezes randomly on 1 client at a time (white pale screen over the game - "not responding" on the header and the "close program or wait to respond" windows message)
I believe this happens when i click and alt tab "too fast" but it happens more often on the laptop lately even though i am careful with my actions speed - plus sometimes multiboxing requires a lot of clicks in order to stay alive. 1 client freezes the other remains unaffected, like i said, and the "frozen" character will remain in space and in fleet and will keep shooting at its target until i either force close the client or i connect another instance of the account. Its always the client i am "using" at the time that freezes or the client i am tabbing into. This has happened even when i run 1 single client windowed mode and it usually happens in npc sites (either mission or sleeper sites since that's what i am running) and when i actually click (when i do something not when idle).

I have 1 eve installation and launch all clients from the same regular launcher (slow as hell these days). Before Rubicon everything was fine, after Rubicon its not, please fix. TY

-Gio
Necharo Rackham
The Red Circle Inc.
Ministry of Inappropriate Footwork
#47 - 2014-01-01 16:53:32 UTC
I have exactly the same symptoms as the above starting right after Odysessy, except I'm running multiple clients on Windows7 without using symlinks. The freezing would consist of one window greying out and not responding until killed - while this was happening whatever action I was performing in game would continue and I'd stay in game until I killed the client (the Windows Error was AppHangB1)

Originally, it was always consistently one particular user that would have the issue - and usually exactly after warping to a site with any sort of cloud on it. Thinking that it may be file corruption for that one users profile, I reinstalled eve.

Since the last couple of patches it has been consistently happening on every single user, and has occasionally started to happen while only one client was running.

FWIW I have run a memory test, cpu test and looked at temperatures in the system - all of which were running well withing spec.
Grafena Walder
Epilogue Enterprises
#48 - 2014-01-17 09:25:06 UTC
Giorgos Rbs wrote:
I always play windowed mode, and sometimes will run up to 4 clients (usually 2). I have an OK PC at home (i7, GTX660, 12gb ram) and a laptop (i5, Georce GT525M. 4gb ram) that can barely run the 4 windowed eve. Both systems run Win 7 x64.

After Rubicon was deployed both computers started having the same issue. EVE freezes randomly on 1 client at a time (white pale screen over the game - "not responding" on the header and the "close program or wait to respond" windows message)
I believe this happens when i click and alt tab "too fast" but it happens more often on the laptop lately even though i am careful with my actions speed - plus sometimes multiboxing requires a lot of clicks in order to stay alive. 1 client freezes the other remains unaffected, like i said, and the "frozen" character will remain in space and in fleet and will keep shooting at its target until i either force close the client or i connect another instance of the account. Its always the client i am "using" at the time that freezes or the client i am tabbing into. This has happened even when i run 1 single client windowed mode and it usually happens in npc sites (either mission or sleeper sites since that's what i am running) and when i actually click (when i do something not when idle).

I have 1 eve installation and launch all clients from the same regular launcher (slow as hell these days). Before Rubicon everything was fine, after Rubicon its not, please fix. TY

-Gio

I have the exact same issue, except for the following: only 2 characters/clients running at the same time + laptop has a GT540M card.
This began to happen at the same time, i.e. after Rubicon.

Here's what Win7 says:
Problem signature:
Problem Event Name: AppHangB1
Application Name: exefile.exe
Application Version: 2013.11.65.1687
Application Timestamp: 5284d329
Hang Signature: fb6b
Hang Type: 0
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1048
Additional Hang Signature 1: fb6b04c1f36eb030913f9780dd8cf5a4
Additional Hang Signature 2: eff8
Additional Hang Signature 3: eff826a7b7aa00fad1983880fedc189f
Additional Hang Signature 4: fb6b
Additional Hang Signature 5: fb6b04c1f36eb030913f9780dd8cf5a4
Additional Hang Signature 6: eff8
Additional Hang Signature 7: eff826a7b7aa00fad1983880fedc189f
Migal J
Liberam Tempus
#49 - 2014-01-21 09:33:09 UTC
I'm running eve on Ubuntu 12.04 with wine 1.6 in a new PC.

I have random freeze problem since Rubicon when I run multiple clients.

I get complete system freeze and I have to hard reboot.

Here my last .dmp file.

.dmp 1

.dmp 2
Zifrian
The Frog Pond
Ribbit.
#50 - 2014-01-26 01:54:36 UTC
I just started noticing one client freezing up while running multiples on the same machine.

I usually log in 3 accounts but the crashes have happened with 2.
I do play with sound.
I ran some PVP for a few hours and not one crash with one account logged in only.
Every time I have had a crash it has been with two accounts logged in and me doing some sort of PVE in an anomaly. In fact I just lost a ship due to a crash. ><
I have not yet crashed while doing PI or just flying around - it always seems to happen with targeting and/or engaging my drones to a target.
Only my main account (first one logged in?) seems to crash. The others are fine.
I have never had a crash like this in game before.
I am running Windows 7 64 bit, AMD Radeon HD 6700 Series video card with 12.104.0.0 Drivers, and 8 GB of ram.

I have added the tag to the file you suggested. I am not really looking forward to testing it but I will try to do it with rats that do not scram :\ and see if I can get the output file you spoke of.

Let me know what else you might need but at least now I have an idea that it might be due to multi-accounts and I can work around that.

Thanks



Here is my hang error:
Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: exefile.exe
Application Version: 2013.11.65.1687
Application Timestamp: 5284d329
Hang Signature: 4d44
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 4d448c1992573dc113d46f88674d985b
Additional Hang Signature 2: 6bfe
Additional Hang Signature 3: 6bfe71be9b2ea0c3c6e0d560d8a888b9
Additional Hang Signature 4: 4d44
Additional Hang Signature 5: 4d448c1992573dc113d46f88674d985b
Additional Hang Signature 6: 6bfe
Additional Hang Signature 7: 6bfe71be9b2ea0c3c6e0d560d8a888b9

Maximze your Industry Potential! - Download EVE Isk per Hour!

Import CCP's SDE - EVE SDE Database Builder
Previous page123