Absurd crashes since New Fort Update

[Kyrottimus]

I've spoken to a lot of players, and mostly those in MacOS or Linux are experiencing terrible client instability since the new fort update.

We used to have solved this problem by disabling weapon trails and arrow trails, and that fixed our crashes.

Well now, since the fort update, we crash like mad.

I updated my new drivers less than a day ago and still same crashes occur. There was some RO Client update today in the evening sometime and it seems that only made it worse.

I've noticed something too, all of these crashes occur within visual sight of one of the new fort buildings.

Methinks there are some terrible memory leaks within these new forts, and I'd not want to speculate on how to fix them only it's crashing so much (as much as 2-3 times every 15 minutes), it's becoming increasingly maddening.

I'm going to send a crash report each time this happens, hopefully someone notices and takes action.

[Roxxxy]

Since the new forts were introduced, my stability has been extremely bad, to the point of crashing 2-3 times in 15 minutes, too. It's not just near forts for me, though, I can be inner-realm and still crash like crazy. I even sent in a ticket, which was closed with the reply "an update will be released in the coming hours", although that was a week ago.

However, I too noticed the update this evening and even sighed with relief, finally I can play! But no, I crashed twice when logging in, and a third time about 1.5 minutes later. I now cannot play this game, not even by constantly logging back in. It's not fun and I can't go anywhere or fight anyone like this. If this update is the fix I've been waiting for, it has only made things worse.

PLEASE get this sorted out, I have completely ran out of patience with this now. I come here to enjoy myself, not get frustrated...

[hawk0xad9]

It's even worse with the update this evening; I crash instantly when finishing a quest with my lower level alts, and crash when I walk into any decently sized group of players.

From a backtrace log I found in my 'live' folder:

./game(_ZN10ClientBase14save_backtraceEv+0x5f) [0x6646ff]
./game(_ZN10ClientBase12client_crashEi+0x8) [0x664b18]
/lib/libc.so.6(+0x34780) [0x7feedd12b780]
./game(_ZN7MessageD1Ev+0x21d) [0x89e1fd]
./game() [0x898f8d]
./game() [0xe55589]
./game() [0xe55ded]
./game(lua_call+0x2d) [0xe4e07d]
./game(class_gc_event+0xe9) [0xed8019]
./game() [0xe55589]
./game() [0xe55ded]
./game() [0xe5a006]
./game() [0xe5a218]
./game(lua_gc+0xac) [0xe4deac]
./game() [0xecf081]
./game() [0xe55589]
./game() [0xe69646]
./game() [0xe55e3e]
./game() [0xe54877]
./game() [0xe548f5]
./game(lua_pcall+0x66) [0xe50386]
./game(_ZN10lua_actionclEP16ActionableObjectP7Message+0x154) [0x800404]
./game(_ZN16ActionableObject10run_actionEP7MessageP10ActionDataPKci+0xbfb) [0x7b474b]
./game(_ZN16ActionableObject14receive_actionEP7Message+0xcb) [0x7b257b]
./game(_ZN6Entity22input_message_internalEP7Message+0x579) [0x8c79d9]
./game(_ZN9LuaEntity22input_message_internalEP7Message+0x4d) [0x8e7acd]
./game(_ZN6Entity13input_messageEP7Message+0x12) [0x8c4e72]
./game(_ZN11ProxyEntity24receive_message_callbackEP7Message+0x9f) [0x8d1b7f]
./game(_ZN6Entity22input_message_internalEP7Message+0x1ab) [0x8c760b]
./game(_ZN6Entity13input_messageEP7Message+0x12) [0x8c4e72]
./game(_ZN18EntityMessageQueue17process_a_messageEP7Message+0x480) [0x8aa9e0]
./game(_ZN18EntityMessageQueue16process_messagesEv+0x108) [0x8ab698]
./game(_ZN12EntitySystem10poll_frameEv+0x1e) [0x8a608e]
./game(_ZN10GameClient7iterateEv+0x13) [0x5a22f3]
./game(_ZN8MainLoop7iterateEv+0xd) [0x66442d]
./game(main+0x178) [0x5a1d18]
/lib/libc.so.6(__libc_start_main+0xed) [0x7feedd117f6d]
./game() [0x5a1aa9]

[Kyrottimus]

Thank you for sharing your experiences, hopefully more can step forward so we can see a broader sense of what/why this is happening.

My machine info:

LinuxMint 9 Isadora 64 bit (Ubuntu 10 front-end)
AMD X2 64 bit CPU @ 2.7GHz
4 Gig RAM
ATI Radeon HD 4550 with 512mb VRAM and ATI Catalyst 11.5 drivers
Sound Blaster Audigy (original Audigy)

[Roxxxy]

Maybe I'm speaking too soon... waaaay too soon... but the second unannounced update tonight (30 minutes ago) seems to have made things MUCH better! I've been playing for 30 minutes without a crash, which is a massive improvement over earlier tonight!

Still, I guess only time will tell if the issues I had before tonight (the fort patch related crashes, which I assume the OP is referring to) are fixed or not.

Anyway, good luck everyone! I will report back if I spoke too soon

[surak]

Originally Posted by Roxxxy

Maybe I'm speaking too soon... waaaay too soon... but the second unannounced update tonight (30 minutes ago) seems to have made things MUCH better! I've been playing for 30 minutes without a crash, which is a massive improvement over earlier tonight!

Good luck everyone! I will report back if I spoke too soon

Let's pray to

[Kyrottimus]

I don't want to speak too soon, but also for me, it's working well thus far.

Thanks.

[hawk0xad9]

No idea if it will change anything or not, but the random crashes at least stopped for the most part when I play on shader 2. Didn't test the quest thing above though.

Arch Linux 64-bit
Intel Pentium Dual-Core @ 2.20 GHz
2 GB RAM
NVIDIA GeForce 210 (not sure on VRAM, either 512MB or 1GB)

EDIT: If there is another update, I didn't get that either. I'll have to download that later and retest.

[standistortion]

Same here, more crashes after new forts but this evenings client update made the game unplayable, crashed about 15 times in 2 hours.
The area of alsius inner beach near the shipwreck seems bad, crashed 3 times in 10 min there a few days ago.
Warmaster items seem to affect it, noticed this most with ignis player jinfarr in view.
Seems to be affected by chat.

EDIT just tried on max graphics and all ok for 15 min playing

[Roxxxy]

Thank you surak and team! There's nothing better than coming home from a long day of work and playing with friends! You make that possible <3