code causes crash

Grimsin · 01-09-10, 08:48 AM

I have heard people say code will not crash the client. I know thats not true. Or is it? or what in the world... so i have one person who has said the GrimUI causes a crash for them on every load. For awhile now i have been experiencing crashs after i /reload a few times. This morning i was working on my xpbar code more and something i did was causing it to crash on load every time. Ironically it was bug free or at lest according to bug sack it was. No errors in the xml log either. Took out hitsmode and it stopped crashing.

What this tells me is that something with the code is for sure the cause of the crash even if it means the code is overloading the ram for some reason. or something.... anyone have any more insight on exactly why the code can cause crashs.

Dridzt · 01-09-10, 09:32 AM

If you change that to "addon code shouldn't be able to cause client crashes" you're closer to the truth.

What it means is that the client controls the lua sandbox and should be immune to hard crashes from addon code.

In a sense addon code crashing the client is as much a Blizzard problem as it is the addon's.

That said it has happened in the past and there have also been addon authors posting example code on how to make it happen in the hopes Blizzard can make their own handling of the sandbox more robust.

I don't know how one could help you debug it without extensive code review and alot of guesswork.

Grimsin · 01-09-10, 03:27 PM

well i think part of the problem is ram. i think the multiple /reloads then crash is my personal ram issue...

I removed a few addons and it caused the crashing to stop or lessen.

Maybe the whole thing is ram related. to many errors and it overloads maybe?

Slakah · 01-09-10, 05:30 PM

Does WoW spew out an error report?

Phanx · 01-09-10, 05:35 PM

If you overload WoW with Lua errors from addons, it will actually pop up a dialog box warning you that the excessive amout of errors is likely to be slowing down your system, and offering to disable your addons and reload your UI.

Hard crashes with error messages complaining about RAM are more likely due to actual physical problems with your RAM.

That said, I have noticed (though I have absolutely no empirical evidence to back up this observation) that WoW tends to crash if you delete a Lua file that was present when it loads and reload the UI, so if you're developing, and renaming or removing files, that may also be a factor.

Grimsin · 01-09-10, 06:54 PM

hmm that maybe on some of the crashs since i do do that sometimes. i also think that my ram is history but... others are complaining about the crashing issue to.

Grimsin · 01-09-10, 06:56 PM

oh and you mean like the windows error msg? yes. does it spit out an xml error log? oh yea a big one. tons of people have errors in their xml logs lol. of course the grimui core does not at lest not now but...

Elhana · 01-09-10, 07:14 PM

I've had a hard wow crash from wrong frame handling code, so it is possible. Probably best thing you can do is to let wow send error report and keep debugging your own code to find an error.

Polarina · 01-09-10, 08:42 PM

A crash can also be caused because of a bug in the Lua implementation. Please check the Lua's bug site and check if what you're doing is listed there. World of Warcraft's Lua version's 5.1.1.

**Seerah** · 01-09-10, 11:37 PM

I've had a hard WoW crash by accidentally trying to load a texture larger than the 1024 limit (it was 2048).