Pages: 1 2 [3] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Nekopyat
|
Posted - 2008.10.27 16:23:00 -
[61]
Ok, trying to run the client with the debug flags+log as suggested so hopefully I"ll be able to get more details, but here is I what I do know so far:
Starting in Full Screen Switching to windowed (after having logged in) Switching between EvE and Camino EvE client crashes on bringing brought to the foreground Happens both in and outside stations.
I did kill off cider and wineserver which returned a bunch of memory to the system. Nicing the process seemed to help for a while. My top looks like:
Processes: 61 total, 4 running, 57 sleeping... 236 threads 12:22:12 Load Avg: 1.16, 1.10, 1.15 CPU usage: 52.0% user, 11.5% sys, 36.6% idle SharedLibs: num = 172, resident = 35.0M code, 4.99M data, 16.9M LinkEdit MemRegions: num = 13505, resident = 807M + 13.3M private, 249M shared PhysMem: 195M wired, 549M active, 1.03G inactive, 1.76G used, 246M free VM: 14.2G + 127M 228596(3) pageins, 78540(0) pageouts
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE 7909 top 11.3% 0:04.87 1 18 20 1.58M 492K 2.06M 27.0M 7908 cider 97.8% 7:26.82 18 207 1916 342M 138M 366M 4.27G 7907 wineserver 0.0% 0:01.09 2 27 35 192K 32.8M 1.04M 60.1M
With the vsize being of particular worry. |
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.10.27 16:35:00 -
[62]
Originally by: Nekopyat Ok, trying to run the client with the debug flags+log as suggested so hopefully I"ll be able to get more details, but here is I what I do know so far:
Yeah, 4gb seems a little much.
Can you launch CrashReporterPrefs and set it to "Developer" and then make it crash again and look at the trace that it produces? It'll pop up a window. Click "report" and then switch to the tab that shows a big window full of text. It'll show a stack trace. Find the thread that crashed and see if you can paste just that chunk (it should be about ten lines) here -- perhaps along with the name of the process it says crashed and the type/event it says was the cause.
Might help us all figure out if we're seeing the exact same thing, even though the described symptoms already sound similar. |
Nekopyat
|
Posted - 2008.10.27 16:56:00 -
[63]
Originally by: Qordel
Can you launch CrashReporterPrefs and set it to "Developer" and then make it crash again and look at the trace that it produces?
Already had the crash and sent that in, but now I've set the crash report pref an am running again to see if I get it again. |
Hartlier Xirone
Caldari Deep Core Mining Inc.
|
Posted - 2008.10.28 19:28:00 -
[64]
Have tested EVE for 1-2 hours in WIndowed Mode, get about 5-10FPS lower AVG.FPS, otherwise it seems quite stable.
Got one more of these random crashes during a Kill Mission again. ___________________________________
"Building the Future and keeping the past alive is one and the same Thing" |
Bernadictus
Caldari BlackScope Black Scope Project
|
Posted - 2008.10.29 10:46:00 -
[65]
Edited by: Bernadictus on 29/10/2008 10:50:03 I'm running the latest patched EVE client on my 2008 iMac too,and I mainly crash when switching my windowed eve with Entourage, Expose, AdiumX, Illustrator, InDesign, Photoshop and a whole load of other applications.
|
WisdomLikeSilence
Federal Defence Union
|
Posted - 2008.10.29 12:44:00 -
[66]
I was having crashes every few seconds. On the advise of another poster here I logged out and logged back in and I havent crashed since. Its a weird thing to do on a mac, since with just one user you never really see the log in screen, but try it.
Im running 3 instances on a new Imac with the 8800 nvidia card. Framerate is ass, but its rock solid now.
|
droii
|
Posted - 2008.10.30 13:38:00 -
[67]
Yeah, unplayable much?
Just 15 min sitting in a pos not touching anything makes it "nosedive". Accualy pressing buttons can make it worse, not always thu. Just dont try to be doing anything else on the computer...that just ends baaaad! (Numerous bugs logged in the system, just posting here to "keep the pressure up".)
Model Name:iMac Model Identifier:iMac8,1 Processor Name:Intel Core 2 Duo Processor Speed:3.06 GHz Number Of Processors:1 Total Number Of Cores:2 L2 Cache:6 MB Memory:2 GB Bus Speed:1.07 GHz
Chipset Model:NVIDIA GeForce 8800 GS Type:Display Bus:PCIe PCIe Lane Width:x16 VRAM (Total):512 MB Vendor:NVIDIA (0x10de) Device ID:0x0609 Revision ID:0x00a2
|
Verite Rendition
Caldari F.R.E.E. Explorer Elitist Cowards
|
Posted - 2008.10.30 19:08:00 -
[68]
Originally by: droii Yeah, unplayable much?
Just 15 min sitting in a pos not touching anything makes it "nosedive".
For some reason POSs just **** the EVE client, it happens under Windows too. The difference tends to be that the Mac client is doesn't have much in the way of performance it can shed before it's grinding to a halt. ---- FREE Explorer Lead Megalomanic EVE Null-Sec Player Influence Map http://dl1.eve-files.com/media/corp/Veritefw/FWinf |
Morn Judith
Caldari
|
Posted - 2008.10.31 12:24:00 -
[69]
Lots of crashes here as well. Not even two minutes every time, never fails. Weird, i patched, was on for 7 hours, then ran software update for OSX and NOW it crashes. I want to say it conflicted with recent OSX software updates. Good luck guys!!
-Macbook Pro 2.4ghz, 8600gtm, old school client
Quote: Bah, Eve>women. Heck, I left my wife for eve. Well, that and because she had a boyfriend.
|
Batuka
|
Posted - 2008.10.31 15:32:00 -
[70]
Echoing many posts already. Too unstable to run missions/haul through low-sec due to constant crashing. Uploading EVE client again right now to see if this will change. Also horrible graphics since patch as well!
|
|
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.10.31 22:16:00 -
[71]
Originally by: Morn Judith Lots of crashes here as well. Not even two minutes every time, never fails. Weird, i patched, was on for 7 hours, then ran software update for OSX and NOW it crashes. I want to say it conflicted with recent OSX software updates. Good luck guys!!
It's probably the latest client patch and not OSX. When it crashes, are you playing in full screen or in windowed mode?
If you can gather the requested data and open a bug report to CCP on this site, they can use that data to further address the problem and attach it to an internal defect. I haven't seen any indication from CCP that they have all the crash data they need from us, so it wouldn't hurt to send it along.
If you're up for it, just read the first couple pages of this thread including CCP Casqade's instructions for running in debug mode to gather debug logs as well as my comments about setting OSX to gather stack traces and profile info. Then open up a bug, attach the files with a description of your system, problem and how you reproduce it and they should get back to you.
That said, I haven't seen/heard any update to the defect (other than the initial request for a little more info from me) since it was filed more than a week ago. Hopefully we'll at least get some sort of acknowledgement that the problem is understood now or if it's in the process of being fixed or if it's fixed and being QA'd or... whatever (since the report online doesn't seem to really offer a way to get a status on it).
|
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.11.01 02:44:00 -
[72]
Edited by: Qordel on 01/11/2008 02:45:24 From CCP:
Transgaming working on it...
|
Dnaagct
|
Posted - 2008.11.01 15:40:00 -
[73]
I'm crashing a lot running two clients on an iMac 24" 4GB RAM dual core ATI radion HD2600.
The crashes did not happen after patch, when I was running Tiger and launching my lone copy of Eve twice. Crashes started happenening after I upgraded to Leopard, couldn't launch twice and made a 2nd copy. Now they crash frequently on changing windows, especially during session changes. If I don't wait for the session timer to complete before changing windows, one client will crash. And both are super laggy in space now. They weren't using Tiger.
|
Qordel
Caldari School of Applied Knowledge
|
Posted - 2008.11.01 20:44:00 -
[74]
Right, that's not a problem with Leopard though. It's a problem with the Cedega end of the EVE client. The previous patch worked just fine on Leopard and the latest patch started the crashing when in windowed mode.
Clearly there's a difference between Tiger and Leopard that cause different behavior in the same client version, but the problem itself is introduced by the eve (cedega) client; not the OSX upgrade itself.
Certainly is frustrating though.
|
Morn Judith
Caldari
|
Posted - 2008.11.03 23:56:00 -
[75]
Originally by: Qordel
Originally by: Morn Judith Lots of crashes here as well. Not even two minutes every time, never fails. Weird, i patched, was on for 7 hours, then ran software update for OSX and NOW it crashes. I want to say it conflicted with recent OSX software updates. Good luck guys!!
It's probably the latest client patch and not OSX. When it crashes, are you playing in full screen or in windowed mode?
If you can gather the requested data and open a bug report to CCP on this site, they can use that data to further address the problem and attach it to an internal defect. I haven't seen any indication from CCP that they have all the crash data they need from us, so it wouldn't hurt to send it along.
If you're up for it, just read the first couple pages of this thread including CCP Casqade's instructions for running in debug mode to gather debug logs as well as my comments about setting OSX to gather stack traces and profile info. Then open up a bug, attach the files with a description of your system, problem and how you reproduce it and they should get back to you.
That said, I haven't seen/heard any update to the defect (other than the initial request for a little more info from me) since it was filed more than a week ago. Hopefully we'll at least get some sort of acknowledgement that the problem is understood now or if it's in the process of being fixed or if it's fixed and being QA'd or... whatever (since the report online doesn't seem to really offer a way to get a status on it).
I am running it in fullscreen mode, as i never run in windowed mode. Just use alt+tab to switch between apps.
Havent had a problem after that first crash. Crashed again and again, got mad, turned the computer off for the night. Came back to it the next day, played about 8 hour sessions for the next 3 days with only one crash. Weird, but i havent been able to get it to crash again for bug report info.
Quote: Bah, Eve>women. Heck, I left my wife for eve. Well, that and because she had a boyfriend.
|
Apple Boy
Gallente Federation of Freedom Fighters Executive Outcomes
|
Posted - 2008.11.04 06:33:00 -
[76]
currently 1441 works great for me besides the graphics issues that I can deal with, although I'm not excited to go into huge fleet combat with it. 1481 has the graphics issues solved but is just way too unstable. I've been messing around with the sisi client, but it still has the graphics issues . The upside is it's more stable than 1481, downside is it isn't as stable as 1441 and I have yet to be able to consistently reproduce any of the crashes.
|
|
|
|
Pages: 1 2 [3] :: one page |
First page | Previous page | Next page | Last page |