Pages: [1] 2 3 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.10.23 20:38:00 -
[1]
So we can show CCP the degree to which the newest client update is troubling us, please post here if the 1.1.2 update from a few days ago has made the game unplayable due to crashes to desktop.
Mention your system, videocard and frequency, if possible.
----------
I'm crashing an average of every few minutes. Even just sitting in a station doing nothing. Sometimes before even fully logging in. Sometimes after five or ten minutes.
Mac Pro 8-core 2.8ghz w/ 16gmb ram and GeForce 8800
Have completely removed EVE and reinstalled it. No luck. Problem begam minutes after upgrading the client. |
Dr Sheepbringer
|
Posted - 2008.10.23 20:45:00 -
[2]
But hey in Live Dev Blog they said it's quite stable now :) |
Suzie Sly
|
Posted - 2008.10.24 00:16:00 -
[3]
iMac dual-core 3.06Ghz 24" with 4Gb ram and GeForce 8800 (i.e. current top of range iMac). Dual screen - native + a 1600*1200 lcd plugged in.
Since patch lucky if 1 instance stays up and running, especially if I switch to another app such as Firefox.
Starting a second instance is a pure falacy... doesnt last more than a few seconds.
No matter what i do i cant get the client to start in windowed mode - and yes I had it workin fine pre-patch and have tried the same setting changes since.
Tonight I'm going to delete my cache settings etc. but quite frankly dont see why I should have to setup my screen each time theres a patch.
If it doesnt work I'll look to see how effective it is to restore the game pre-patch - thank god for time machine! ...
Overall pretty hacked off... 3 accounts and I can only view 1 at a time... prepatch I used to run all 3 fine albeit the 2nd and 3rd had small windows to reduce overheads.
Now... considering letting one of more of the accounts expire till I can dual log again.
|
Kirkus Jameus
Amarr Guardian Gold Rakashasa Corporation
|
Posted - 2008.10.24 00:24:00 -
[4]
I don't know that I'd call it entirely unstable, however I would say that it is now the worst it has been since I started playing last November.
It used to crash to desktop once in 6-8 hours, sometimes not for 10-12. Now it happens sometimes in 30 min, sometimes right at login.
I never used to lose connections. Since the patch it has happened maybe a dozen times. Most annoying!
I always start fresh after a reboot and never run any other programs while playing Eve. iMac 1.83ghz, 2GB X1600 (i think.)
Most recent patch rendered the inside of stations black except for a few scattered light effects. No big deal really, but would be nice to have back to the way it was. (Who doesn't twirl their ship once in a while?)
After the October 8 patch my FPS drop from 6-10 during a mission battle to 1-3. Now the FPS is back up but there is the station and map lines issues.
Drones are unreliable at best. They sometimes drift away from each other. They go off and attack random targets. They don't always return when told to. This never used to happen to me before.
That's my story so far.
KJ
I can get by for now as long as I don't risk low or null sec...
|
Andrew Highwind
Caldari State Secret Service
|
Posted - 2008.10.24 00:42:00 -
[5]
I'm not quite at the point of unuseable, but it's getting pretty close. The client will crash almost without fail if I switch to it using Spaces. I haven't ran multi clients yet, but after reading responses in other threads, it doesn't sound like a good idea. Even the SiSi client is starting to misbehave.
I haven't played long enough in a day since the patch for the client to get fubar'd.
I'm rolling with a 2.4Ghz iMac with the ATI RadeonHD 2600 256MB VRAM, the machine has 4GB of ram. Meanwhile the game runs perfectly fine on my brand new MacBook, for some reason, I find this hilarious.
|
|
CCP Casqade
|
Posted - 2008.10.24 01:06:00 -
[6]
Hi all.
Just so you know, we are aware of that some peoples stability have gone down, a lot. We are working on a solution short term and long term. Those of you who have crash occur, and then another crash as soon as you enter the game again. Can you please try the following:
1. After the first crash occurring, do not relaunch the client 2. Start the Activity monitor 3. Check if you see if there is a "cider" or "wineserver" process running. 4. If so, please type the following into a terminal window "killall -9 cider wineserver" 5. Launch EVE again
Does this help at all?
Those of you who are experiencing these crashes, can you also please try the following in terminal:
1. Open Terminal 2. "cd ../.." 3. cd Applications/EVE\ Online.app/Contents/MacOS 4. ./cider -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log 5. Have the crash occur 6. Compress the logfile generated on your desktop 7. Attach to a bug report with the title "Mac crash issue - For Casqade" 8. If the file is too big, please upload it to EVE-Files or a similar file site.
Thanks
|
|
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.10.24 01:44:00 -
[7]
I'll perform the above steps next time I start up and wind up with a crash. I had considered gathering a core and pstack (or whatever the OSX equivalent is) for a bug report, but hadn't yet discovered the steps for doing so in OSX (presuming there is a 'coreadm' equivalent).
Anyway, thanks for the comment. Wasn't looking to rag on CCP with this post, but rather gather people with the same problem together in one spot (there have been lots of individual threads on it) so that you guys could see what we're up against and/or at least acknowledge that you're aware of it being an issue.
|
Anton Brienne
|
Posted - 2008.10.24 05:09:00 -
[8]
Just submitted a bug report... hopefully this'll be resolved soon. Casqade: No cider or wineserver processes are left running on my computer after crashes. I think it may have something to do with running the client in a window; when I run full screen it doesn't crash before I can log on (which it normally does) but I haven't tried any serious playtesting, so I could be totally wrong. Oh, and the station interiors still aren't displaying properly, as would be suggested by the latest patch notes. Just FYI. |
Tank Charlie
Caldari Blacksheep Incorporated
|
Posted - 2008.10.24 05:43:00 -
[9]
I run 3 instances of Eve on my 15" MacBook Pro.
When I saw the update come out a couple days ago, I downloaded/patched my first instance. That instance has been quite predictable ... it crashes any time another application comes to the foreground. My other two instances of the Eve client, both unpatched, have been much more stable.
I'll see if I can get crash logs from the first/primary install ... but it's definitely been a step in the wrong direction. |
|
CCP Casqade
|
Posted - 2008.10.24 10:46:00 -
[10]
Originally by: Qordel Wasn't looking to rag on CCP with this post, but rather gather people with the same problem together in one spot (there have been lots of individual threads on it) so that you guys could see what we're up against and/or at least acknowledge that you're aware of it being an issue.
Much appreciated.
Originally by: Anton Brienne Just submitted a bug report... hopefully this'll be resolved soon. Casqade: No cider or wineserver processes are left running on my computer after crashes.
Thank you.
Originally by: Anton Brienne
I think it may have something to do with running the client in a window; when I run full screen it doesn't crash before I can log on (which it normally does) but I haven't tried any serious playtesting, so I could be totally wrong.
Interesting. Are you running it using the window mode switch in the config file to start it up in window mode? If you are running it in full screen, do you eventually get the crash too?
Originally by: Anton Brienne
Oh, and the station interiors still aren't displaying properly, as would be suggested by the latest patch notes. Just FYI.
Explanation: http://oldforums.eveonline.com/?a=topic&threadID=903116&page=1#10
Originally by: Tank Charlie
That instance has been quite predictable ... it crashes any time another application comes to the foreground.
I'll see if I can get crash logs from the first/primary install ...
Thank you. Good reproduction usually help even more. It is important to give us information about the circumstances like; are you starting the client in window mode? Are you switching it to window mode after start? What program is it that comes up in the foreground?
Originally by: Tank Charlie but it's definitely been a step in the wrong direction.
We fully agree. |
|
|
Shin Chogan
|
Posted - 2008.10.24 15:47:00 -
[11]
Edited by: Shin Chogan on 24/10/2008 15:49:19
Originally by: CCP Casqade
Originally by: Anton Brienne
I think it may have something to do with running the client in a window; when I run full screen it doesn't crash before I can log on (which it normally does) but I haven't tried any serious playtesting, so I could be totally wrong.
Interesting. Are you running it using the window mode switch in the config file to start it up in window mode? If you are running it in full screen, do you eventually get the crash too?
I've come to the same conclusion as well. It is suspiciously coincidental with bringing another app to the foreground. I've not tried it full screen yet.
By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
I've not run eve from the terminal yet - my crashes don't appear to be as frequent as some here, I can play for an uninterrupted hour or two (as long as I don't switch apps) But I've noticed a lot of error messages in the console logs that weren't there pre patch. I'll raise a bug report as you suggested but the short version is a lot of messages like the following : _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
Any chance you could release an UN Patch Patch ;)
|
Ami Nia
Caldari
|
Posted - 2008.10.24 15:47:00 -
[12]
It has been unstable for me, so I switched back to the unpatched client.
It did crash almost every time when switching to another app and back (especially if the other App happened to be on a different workspace). But I was running with "GLSL" = "Y" (no problem with stations as I have "load station environment" unchecked).
I now switched back again ONE of my client installations to the patched version and changed "GLSL" = "M". It seems to be a bit more stable, after that. I'll keep using the patched version and if I find a way to crash it reliably I'll produce a crash log.
One thing that I think I already suggested somewhere else is to confront with cedega and verify with them if it's possible to find a way to run the logserver (the one you use in windows) somehow. I'm not sure how the client talks to the logserver. I guess it's either a standard TCP/IP socket or a pipe. If it's a socket, having it running should be extremely easy. If it's a pipe, they should be able to remap the Windows pipes API calls to either a TCP/IP socket or unix pipes. If they do that we'd be able to provide both the "standard" log data and the cyder log data. I think this would make things much easier for everyone.
Originally by: CCP Mitnal So we can 1 v 1 with Garmon.
|
Ami Nia
Caldari
|
Posted - 2008.10.24 16:03:00 -
[13]
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
Originally by: Shin Chogan _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
That means that cider did start a new thread that (directly or indirectly) uses Objective C data but forgot to setup a pool. It's a sign that something should be fixed and that some memory is probably being leaked, but it should not be too worrying and is probably unrelated to the crashes and instabilities.
It MAY have something to do with performance/instability that is noticeable after a long time playing, however. But it's easy to verify if that's the case: keep Activity Monitor up and check how much the application "eats" memory over time.
|
Shin Chogan
|
Posted - 2008.10.24 16:36:00 -
[14]
Originally by: Ami Nia
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
I was going to yes ... however doing a double check ... ooopps Wrong directory !!!!
<slaps self> Way to go shooting my mouth off :/
|
Paula Quartz
|
Posted - 2008.10.24 17:03:00 -
[15]
Originally by: CCP Casqade
Those of you who are experiencing these crashes, can you also please try the following in terminal: [etcetera]
Did that, and just posted the petition. |
Ami Nia
Caldari
|
Posted - 2008.10.24 19:31:00 -
[16]
Casqade, I've filed a bug report (id 64273) as for your instructions. I've attached a zip file with some stuff, including a MyMachineConfig.txt file with details of my settings and a some more explanations.
I'm posting the last three paragraphs of that file here too:
I had a look at the crash log. The exception is an invalid instruction execution trap. I cannot say (well, probably I could if I really wanted to hack this info out, but I'll leave you the pleasure to do it. Besides ... it may be against the EULA!) if it's inside the cedega code or inside the python code (not the python source probably, but it could be in some python C library or in the python itself). In any case it should not bee to difficult for CCP/Cedega to find out.
I've seen from the crash log that the cedega code reacted to the exception by creating ntdll_crashReport.txt and ntdll_minidump.dmp in the "P: drive". So I went to the preferences dir that is mapped to P: and took those files too. They are attached for your enjoyment.
My personal petition to you: fight for keeping the mac-patch optional until we are VERY sure it's allright. Especially across the Midas (or whatever "rising" they call it now) deployment. Have that deployment go with an unpatched client and then post an optional patch for macs again. This will save us (and you too) from hell.
|
Ami Nia
Caldari
|
Posted - 2008.10.24 19:38:00 -
[17]
Originally by: Ami Nia
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
Originally by: Shin Chogan _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
That means that cider did start a new thread that (directly or indirectly) uses Objective C data but forgot to setup a pool. It's a sign that something should be fixed and that some memory is probably being leaked, but it should not be too worrying and is probably unrelated to the crashes and instabilities.
It MAY have something to do with performance/instability that is noticeable after a long time playing, however. But it's easy to verify if that's the case: keep Activity Monitor up and check how much the application "eats" memory over time.
After monitoring the memory consumption and looking at the crash log I must say I'm nearly certain the "leak" is a non issue. It only happens at the very beginning, therefore no over-time-memory-leakage should be experienced.
Plus when EvE starts you see a process going up, then launching another process and finally dying out (look at the dock during startup). I'm 99% confident that it is the launcher process that has a thread that misses the Objective C memory pool initialization, therefore all the memory is actually reclaimed by the OS when that thread dies.
|
|
CCP Casqade
|
Posted - 2008.10.24 20:10:00 -
[18]
Originally by: Paula Quartz Edited by: Paula Quartz on 24/10/2008 17:21:59
Originally by: CCP Casqade
Those of you who are experiencing these crashes, can you also please try the following in terminal: [etcetera]
Did that, and just posted the petition.
Edit: and another one send in. I hit my petition limit, so I switched e-mail addresses :)
Anyone up for a 'crashlogs delivered' competition?
Do not file petitions about this! These are bug reports and should go into the bug report system. Petitions go to Game masters/Customer support. Bug report system: https://bugs.eve-online.com/newbugreport.asp |
|
Shin Chogan
|
Posted - 2008.10.24 20:25:00 -
[19]
Originally by: Ami Nia
Originally by: Ami Nia
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
Originally by: Shin Chogan _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
That means that cider did start a new thread that (directly or indirectly) uses Objective C data but forgot to setup a pool. It's a sign that something should be fixed and that some memory is probably being leaked, but it should not be too worrying and is probably unrelated to the crashes and instabilities.
It MAY have something to do with performance/instability that is noticeable after a long time playing, however. But it's easy to verify if that's the case: keep Activity Monitor up and check how much the application "eats" memory over time.
After monitoring the memory consumption and looking at the crash log I must say I'm nearly certain the "leak" is a non issue. It only happens at the very beginning, therefore no over-time-memory-leakage should be experienced.
Plus when EvE starts you see a process going up, then launching another process and finally dying out (look at the dock during startup). I'm 99% confident that it is the launcher process that has a thread that misses the Objective C memory pool initialization, therefore all the memory is actually reclaimed by the OS when that thread dies.
I've noticed these entries appearing when I dock as well. |
Paula Quartz
|
Posted - 2008.10.24 20:39:00 -
[20]
Originally by: CCP Casqade Do not file petitions about this! These are bug reports and should go into the bug report system. Petitions go to Game masters/Customer support. Bug report system: https://bugs.eve-online.com/newbugreport.asp
Ah, I see, apologies. Would you like me to re-submit them there? Got your name stamped on 'em in the petitions, so they should reach you. |
|
Ami Nia
Caldari
|
Posted - 2008.10.24 22:18:00 -
[21]
Originally by: Shin Chogan I've noticed these entries appearing when I dock as well.
I'll do some more checks then.
|
Tridik
Caldari the united
|
Posted - 2008.10.25 00:51:00 -
[22]
Macbook pro -
Im having tremendous issues while running my client. It randomly crashes to desktop after this latest patch.
|
Anton Brienne
|
Posted - 2008.10.25 02:02:00 -
[23]
Originally by: CCP Casqade
Interesting. Are you running it using the window mode switch in the config file to start it up in window mode? If you are running it in full screen, do you eventually get the crash too?
I Cmd-Enter to enter windowed mode immediately after starting the game. It seems that entering windowed mode and switching apps before actually entering the game (i.e. while logging on) causes more instability, for me at least. If I leave the game fullscreen until actually in-game, it is then much more stable. I can always create a crash by starting the client, entering windowed mode, beginning to log-in, switching applications, then switching back to eve. Sometimes it actually gets as far as starting the game proper, but it always crashes in a minute or two at most. Waiting until in-game to switch apps gives me half an hour or so. I haven't had any crashes while in full screen, but I frankly can't stand to run the thing fullscreen for any length of time, so I'm not sure if it'd eventually happen. It seems to be linked to running in a window, though.
|
beta6
|
Posted - 2008.10.25 03:50:00 -
[24]
I'm Running Imac intel core duo 2.4Ghz 1Gb RAM ATI,RadeonHD2600 OS 10.5.5 .
I run two accounts in windowed mode on the mac client. I can not go longer then 40 min with out a crash after the latest patch. To be honest I'm getting tired of all the sh*tuff I have to do to try and get the client playable. Last time I checked I pay CCP to do that so I can PLAY eve. Engage in activity for enjoyment and recreation rather than a serious or practical purpose. <--PLAY
|
Apple Boy
Gallente Federation of Freedom Fighters Executive Outcomes
|
Posted - 2008.10.25 05:46:00 -
[25]
Edited by: Apple Boy on 25/10/2008 05:46:50 next time I reboot back to OS X I'll create the logs and submit, but in the meantime from memory, current ways to reproduce various crashes: - startup the client, and then in rapid succession cmd+tab between eve and something else while in full screen mode. (had this issue since day one) - startup the client, cmd+return to switch to windowed mode, cmd+tab between windows and it'll crash (only since latest patch) - startup the first client, switch to windowed mode, startup second, just let them idle. guaranteed to crash both (only since latest patch)
I have a second generation macbook pro, model number: MA611LL/A http://support.apple.com/kb/SP24 it's running leopard |
Summer Fire
|
Posted - 2008.10.25 07:12:00 -
[26]
Since the patch I have no longer been able to run 2 clients. While running 2 was never trouble free at least I was able to play the game. I start one, wait a few minutes then start the other. Within 3 mins I am getting serious frame rate drop then the 2nd instance crashes. It is never the first instance. No disconnect just crash. After combing the net and boards for more info and finding nothing new I started playing with only one client. Got tired of this very quickly and thought that if I ran both clients in a reduced window it might ease things... BINGO. Been playing for 10 hours without a problem. Graphics card issue perhaps? The frame rate is still not good and oddly the 2nd client has a better rate than the first.
Another small issue is that each time I log on now I get a new mail reminder. There is no new mail.
Finally, Why is one instance of the client so much larger in terms of RAM and Virtual RAM. One is much older character of course but does this increase memory so much ? PID Process CPU RSIZE VSIZE Time Prts RPRVT 1262 EVE Online40.6855.70 MB1.80 GB56:12.69249859.70 MB1,790,2621,656,035108.45 MB22 1099 EVE Online49.3590.78 MB1.39 GB1:34:33.72255584.19 MB3,386,7943,139,786139.03 MB22
iMac 2.8Ghz, 4GB RAM, 1 TB HDD, ATI Radeon 2600HD 256MB
|
Shin Chogan
|
Posted - 2008.10.25 08:01:00 -
[27]
I tried starting and running in fullscreen last night, normally I play in a window, and despite many attempts to crash my client I couldn't - about 3 hours of uninterrupted play.
|
Paula Quartz
|
Posted - 2008.10.25 10:39:00 -
[28]
I'm not sure if it's true, but I recognize the "don't switch programs" sentiment. When I run the client and I want it to stay up for a while (e.g. waiting for an upcoming skill completion), I try to keep the Eve window active as much as possible. Didn't have the fear of switching with the old client. I could easily mail, browse and watch videos with that.
|
Bit Steen
|
Posted - 2008.10.25 11:01:00 -
[29]
I have a lot of crashes too - much more then before the patch
System: Mac Pro 2.8ghz, NVidia 8800GT, 14gb Memory and OS X 10.5.5 |
Srg Hedge
|
Posted - 2008.10.25 11:11:00 -
[30]
Hi CCP Casqade. My mac book pro NEVER and i quote crashed until this patch and from happening every 10 or so minutes it is happening every 1-2 minutes even doing nothing! ------------------------------------- MBP-2.6ghz-4gb-200gb 7400rpm-8600gt
|
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |