Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
LnX0R
|
Posted - 2009.08.03 19:28:00 -
[1]
So, hi guys,
i am playing eve online since half an year (or a little few) with slackware 12.2 and an nvidia graka without (greater)Problems, there was only the Loginscreen crash, wich is fixed so far.
But today an error occurs, wich is a little starnge. My Eve Application crashes after the login, when the news on the character selection screen should be loaded OR after char selection when "entering station" should occure (80% entering game as lnx0r is the status).
Error message is sometimes "Error in C++ runtime library" but mostly the debug box wich says that the application crashed.
in the terminal the message is: fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 00002746 wine: Unhandled page fault on read access to 0x45455246 at address 0x45455246 (thread 001a), starting debugger...
wich looks similar to the message wich occured a few months ago in the login screen...
but eve runs perfect for months now and i changed nothing...this morning it worked all fine. Any suggestions? i cand find a solution on my own...
best regards, LnX0R
|
Spoofeydoo
Caldari Nova-Tek Mostly Harmless
|
Posted - 2009.08.03 23:36:00 -
[2]
What program and version are you using to run eve online? If it is wine try using 1.1.23, it seems the most stable for me.
|
Miraqu
Caldari Marquie-X Corp Atropos.
|
Posted - 2009.08.04 05:36:00 -
[3]
Thats the ususal page fault crash in recent wine versions (.25+). For some users eve crashes instantly, for some once a few days.
wine below .25 is considered stable, since the commits were introduced with .25.
|
LnX0R
|
Posted - 2009.08.04 08:25:00 -
[4]
Edited by: LnX0R on 04/08/2009 08:26:04 Oh, sorry, i fergot that... Iam using wine 1.1.20 and tried now with 1.1.23, but i get the same error...it never occurs before and i didnt change anything :( The only thing i chnaged, was to extend my account by paying by Timecard...but that i did sometimes before, too^^
|
Solbright
Advanced Security And Asset Protection
|
Posted - 2009.08.04 12:39:00 -
[5]
Clean out Eve's cache files ... Disable sound ... Reinstall Eve ... Reinstall Wine ... Clean inside of PC ... Check for lose connectors/CPU/graphics card ... Resocket RAM ... Replace power supply ... Replace everything.
----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up! |
Solbright
Advanced Security And Asset Protection
|
Posted - 2009.08.04 12:43:00 -
[6]
Edited by: Solbright on 04/08/2009 12:44:49
Actually, you may want to double check you aren't running Wine 1.1.25 or later.
$ wine --version
----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up! |
LnX0R
|
Posted - 2009.08.04 14:31:00 -
[7]
Well checked everything, removepkg wine + clear /.wine folder done, hardware checked, reinstallet newest Nvidia drivers, wine 1.1.23, eve premium full client ... Now th error occurs in login screen.
|
Miraqu
Caldari Marquie-X Corp Atropos.
|
Posted - 2009.08.04 14:44:00 -
[8]
If it correlates with the time, how about a netdate/ntpdate or such?
Wine would crash for me with a borked system time in WoW, WC3 (online) and farcry (lan).
|
LnX0R
|
Posted - 2009.08.04 20:18:00 -
[9]
well, thats right, wine is very "timedepent", but what i was trying to say in my broken english (...) was, that it ist like an trigger... in background there is thread 001a or 001e or 0019(in login)wich calls for ntdll.I really dont know what happens in that dll, its a winKernel dll wich has some more and different functions, thats what i know. I cannot say what its trying to call @ offset 0x000048f4 at address (and so on) or if it is an audio, grafik or netcard call or anything else...but there it crashes...well, i try on...
P.S.: I made a chronjob know for systime, thanks for that :)
|
Solbright
Advanced Security And Asset Protection
|
Posted - 2009.08.05 01:59:00 -
[10]
That's nothing but a bull**** joke that the timestamp affects Eve. And why you would think Wine is affected by such a thing is beyond me.
LnX0R: You may be looking at hardware problems there.
----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up! |
|
LnX0R
|
Posted - 2009.08.05 16:15:00 -
[11]
Edited by: LnX0R on 05/08/2009 16:15:51 Yea, not the timestamp, but the timedifference could cause probs,in fakt its not, but wine crashes very fast if you got disco or timed out.
i investigated the errors again, and there is always(!) that line: fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 00002746 before the unhandled page fault read access to ...
but the problem now, it is an fixme and no bug, wich means that wineHQ wont care immediatly On other side, it workes on other pcs with that version and that /.wine dir.
And the edit...now it works fine, after i give up trying... thats really strange.
Fly safe :)
|
Essial
Caldari McCulla Alliance
|
Posted - 2009.08.05 18:23:00 -
[12]
This sounds like memory trashing. This kind of problem is interesting and annoying in the fact that the problem doesn't directly cause a "memory" error, but instead causes some other type of error - usually something random and different every time. With the latest versions of wine, there was a change (NOT a bad commit) that deals with freeing and handling memory. The code works as expected. HOWEVER, a lot of games have a flag that tells windows (and Wine) that it can run in higher memory (>2gb) (read: VIRTUAL address space, not physical memory), yet uses D3D9X which CANNOT run in high memory. At some random point a condition causes the app to be moved and pulls the D3D9X code outside of low address space, causing the pointers to all be incorrect - which obviously creates a random crash. To remedy this, a new patch has been created for WINE that disables messing with lower areas of memory, which fixes this problem. Again, note this is NOT a problem with wine so much as a bug in the applications, that windows happens to deal with in a way that is different than expected. Older versions of wine don't have this issue, but being an older version - typically have issues with other things dealing with DirectX and audio and such. The best way around this I have found is to simply build WINE from source, and apply said patch. That way you have all of the latest features of wine, as well as the fix to play EVE and other games without random crashing.
|
LnX0R
|
Posted - 2009.08.05 21:35:00 -
[13]
Ok, that sounds very interessting and like an good explanation for that problem, i will try something with that next time. Thank you all for your help very much.
|
Solbright
Advanced Security And Asset Protection
|
Posted - 2009.08.06 00:22:00 -
[14]
Originally by: LnX0R Yea, not the timestamp, but the timedifference could cause probs,in fakt its not, but wine crashes very fast if you got disco or timed out.
It's all rubbish, system time diffs are not important to Eve or Wine. What I meant by "timestamp", maybe not a good choice of words, was the system date and time. Which is quite a separate thing from game timings.
Wine does not crash on disconnects or timeouts. Eve might show some lag effects or desync issues. That's about all.
----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up! |
Solbright
Advanced Security And Asset Protection
|
Posted - 2009.08.06 00:39:00 -
[15]
Originally by: Essial ... a lot of games have a flag that tells windows (and Wine) that it can run in higher memory (>2gb) (read: VIRTUAL address space, not physical memory), yet uses D3D9X which CANNOT run in high memory.
C would have to be the root cause of this type of bug. Allowing signed pointer comparison invites buggy code. That said, it doesn't really excuse M$ for DirectX flaw.
Question, Is this "flag" actually part of DirectX?
----- The Eve Client - A Love Story - The single biggest fix CCP ever did to Eve. Keep it up! |
Essial
Caldari McCulla Alliance
|
Posted - 2009.08.06 01:41:00 -
[16]
Originally by: Solbright C would have to be the root cause of this type of bug. Allowing signed pointer comparison invites buggy code. That said, it doesn't really excuse M$ for DirectX flaw.
Question, Is this "flag" actually part of DirectX?
I can't believe I didn't think about that. Well really I could. Signed pointer? WTF? I'm not doubting what you are saying, I'm simply in shock that such a thing would EVER exist.
As far as the flag, I really have no idea, but I would guess it has to do with some of the parameters of the EXE itself, because otherwise you would THINK the DLL would have the flag set properly if each module had its own flags.
This is why WINE is such a complex piece of software -- you cannot simply read the description of a method and implement it word for word. No, microsoft code is more like a woman -- says it does something, but really DOES something else entirely (joking of course) that just so happens to also do what it claims to do :)
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |