Weird ongoing crashing, fatal error in main thread

[Silresa]

Having some weird crashing issues with a server - note that many players are NOT having it and some are, and it happens primarily with certain zones (usually the same ones for people who have the issue.)

Things I have tried:
Adjusting memory usage settings, texture quality, pixel shaders, texture streaming
Adjusted eqclient to have a normal ratio when playing windowed
Set exe to run in compatability mode, dpi scaling off, run as admin
Updated every redist I can find related to eq/eqemu recommended on the forums for eqlive and eqemu for c++ runtimes
Did the same for directx
Deleted eqclient.ini and started fresh
Grabbed a fresh uifiles folder from someone without a crashing client and overwrote mine (also redownloaded appropriate sarsexp and tried that)
I've updated video and sound drivers as well

I do run two boxes, not sure if that would cause it to screw up in this fashion, but many other players on the same server are doing the same (I also made a copy of my directory and run each instance from a different folder, just to be safe. )

I just double-crashed so it doesn't wanna crash now of course since I just relaunched my clients, but if the specific data in the "fatal error in main thread code" is useful I will be more than happy to post it in a follow-up.

Thanks!

There seems to be two parts to the error: Sometimes it hapens while in zone and I can just not click okay on the error and keep playing.. but any textures which haven't yet loaded will not load. It's just endless expanses of gray shapes and character models without textures.

The other part is it will crash when zoning (if I zone after ignoring a crash it was always 100% crash, leading me to believe it's pretty much the same thing.) This happens to a lot of people playing, but only some, despite having identical files/UIfiles/etc.

I'm really at a loss and would appreciate any help at all. The relevant part of the crash log seems to be a fatal error in main thread - and again some players get this same crash at the same zone almost always, others haven't had it happen even once. :( Logging back in and continuing is generally more or less fine, but zoning several times, especially into some zones, tends to make it happen.

Pretty sure it's the ROF2 client, for what that's worth.

[Silresa]

Here is a snippet of the actual dbg when the crash happens -

[Sun Jul 15 21:01:20 2018]02203:fatal error in main thread Code = e06d7363 ADDR=0x7634ddc2

[Sun Jul 15 21:01:20 2018]02204:EAX=0068c2a0 EBX=0068c48c ECX=00000003 EDX=00000000

[Sun Jul 15 21:01:20 2018]02205:ESI=636c8c68 EDI=63761d18 EBP=0068c2fc ESP=0068c2a0

[Sun Jul 15 21:01:21 2018]02206:Fatal error occurred in mainthread! (Release Client #630)

[Sun Jul 15 21:01:21 2018]02207:Client Version: May 10 2013 23:30:08
[Sun Jul 15 21:01:21 2018]02208:Skin Directory: UIFiles\default\

[Sun Jul 15 21:01:21 2018]02209:Graphics DLL Loaded: Graphics DLL Version 2.00.70657
[Sun Jul 15 21:01:21 2018]02210:Graphics Build Date: May 10 2013 23:31:07
[Sun Jul 15 21:01:21 2018]02211:Video Card: NVIDIA GeForce GTX 1080, 24.21.13.9836

[Sun Jul 15 21:01:21 2018]02212:Crash (char = Silresa, zone = drybone)

[Sun Jul 15 21:01:21 2018]02213:Local Player's World location at time of crash: 1784.000000, -1030.000000, 60.750000.

[Sun Jul 15 21:01:21 2018]02214:Gamestate at crash = 253

[Sun Jul 15 21:01:21 2018]02215:Processor: 12 of type 586
[Sun Jul 15 21:01:21 2018]02216:Memory: Load: 45, Total Phys: 16277, Avail Phys: 8946, Total Page: 19961, Avail Page: 9484, Total Virtual: 2047, Avail Virtual: 144, FreeBlocks: (FRAGMENTED) 14,8,8,5,5,4,4,4,4,3
[Sun Jul 15 21:01:21 2018]02217:Pools: Temp: 12649220(12447524). Persistent: 200773655(200723043). OnDemand: 0(0). Zone: 5641136(5560778)
[Sun Jul 15 21:01:21 2018]02218:MaxTextures: 62369k, CurrentTextures: 16408k, HighQualityTextures: 16408k
[Sun Jul 15 21:01:21 2018]02219:CPU: Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz 3396186

[Sun Jul 15 21:01:21 2018]02220:Memory Mode: Balanced

[Uleat]

I haven't heard of this..and RoF2 acting like this is really odd.

I see 'drybone' in your log there, any more zones in particular?


EDIT:

I'm running a fairly recent version of the peq database..and I don't have a 'drybone' entry.

Are you playing on a custom server that has added this in manually?

[Maze_EQ]

Is this the infamous Sanctuary crash?

[demonstar55]

I guess so.

[Silresa]

Yeah, plenty of custom stuff, and the error showed up in several eqemu searches and even lots of eqlive posts! If it was everyone playing Sanctuary having the same issue I'd not really give it much thought, but some people are affected heavily ( like myself! ) and others are not at all and pretty much never crash. Some zones are definitely worse, but haven't seen any real rhyme or reason to the which or why yet. Drybone is one of the old Ykesha zones, the one with the boat and the little outpost and the looong swim to the beach that leads off into the cave, I never remember the names of Ykesha zones.

The weirder past is when I played a few years back I had zero crashing of this sort at all on the same server, it was flawless, and there wasn't any significant changes that'd seem likely to cause it since then.. which again leads me to believe it's somethin' that can be sorted out.

[zerjz3]

Is this the infamous Sanctuary crash?

This issue is brand new and 1 month old, far newer than anything you would have seen over a year ago when this issue wasn't happening. So there isn't anything infamous about it. What are you talking about, exactly, since you haven't played or been involved in Sanctuary since this issue started happening?

I think this player is just trying to find a solution to the problem, and not get the useless input of an ex corrupt GM with an axe to grind.

[Cusser]

This issue is brand new and 1 month old,

[Sun Jul 15 21:01:21 2018]02206:Fatal error occurred in mainthread! (Release Client #630)

Similiar error posted 3 years ago, on the Sanctuary thread, 06-27-2015

http://www.eqemulator.org/forums/showpost.php?p=241271&postcount=51

That error can happen for different reasons with different players, on different servers, but considering you can find that
only "some" players on the same server are having that issue and others are not, the most common involves some kind of
custom alteration to the client, (custom server-client files, patches, etc)

But it can also involve players that have downloaded a "buggy" client from somewhere as well. I always encourage people to
try and find a more reliable (or reputable) source, especially when looking for an RoF2 client. I've played on a couple of
servers where a player downloaded a rogue copy and had all sorts of problems. That copy can easily spread to many others.

Obviously a server and it's players need to come together to deal with the issue, (if they have a support forum).

[Kingly_Krab]

Sounds like he’s either not using your custom patch(es) or isn’t being compliant with the required client version or whatever. Regardless, being it’s an issue due to a custom change, we don’t support it here and it will be on zerjz’ shoulders to solve.

[Maze_EQ]

This issue is brand new and 1 month old, far newer than anything you would have seen over a year ago when this issue wasn't happening. So there isn't anything infamous about it. What are you talking about, exactly, since you haven't played or been involved in Sanctuary since this issue started happening?

I think this player is just trying to find a solution to the problem, and not get the useless input of an ex corrupt GM with an axe to grind.


Actually,

This issue has been present since the launch of Sanctuary, as we've hit it numerous times, and was only resolved by clearing the resources folder in the EQ directory, then repatching.

So. Calm down ya fuckin pyscho.

Google says:

ipconfig /flushdns

/shrug