Rick Posted January 2, 2010 Posted January 2, 2010 I get EXCEPTION_ACCESS_VIOLATION error all the time in the script editor. I can't seem to figure out any sort of pattern. I'll just be typing something, anything and it happens. Then the editor closes down. What's the deal with this error? Quote
AggrorJorn Posted January 4, 2010 Posted January 4, 2010 I have this a lot in windows XP. Crashes for no real reason, except the 4 x tab. Windows 7 doesn't have this problem.. Quote
Rick Posted January 4, 2010 Author Posted January 4, 2010 Yeah, I'm using XP. Not sure what's up with this error. It's annoying because I can't figure out why or when it happens. Quote
AggrorJorn Posted January 4, 2010 Posted January 4, 2010 I don't know what can be done about this. Is there some kind of error log in leadwerks? I have to check that... I'm sure that Josh makes some more try- catches to reduce these errors. I haven't got the slightest idea how this patterns goes. besided 4x tab, I often have it also with quickly commenting several lines of code after each other. Quote
Rick Posted January 7, 2010 Author Posted January 7, 2010 Seriously, this error is driving me insane. Quote
Canardia Posted January 7, 2010 Posted January 7, 2010 Usually this error starts to popup when I initially make an error in LUA code. Quote ■ Ryzen 9 ■ RX 6800M ■ 16GB ■ XF8 ■ Windows 11 ■ ■ Ultra ■ LE 2.5 ■ 3DWS 5.6 ■ Reaper ■ C/C++ ■ C# ■ Fortran 2008 ■ Story ■ ■ Homepage: https://canardia.com ■
Rick Posted January 7, 2010 Author Posted January 7, 2010 But I'm not saving anything, so it shouldn't be trying to run the lua file until I save it. If I have a perfectly running lua file, and then I start editing it, I get the error even without saving it. That shouldn't happen. Quote
Canardia Posted January 7, 2010 Posted January 7, 2010 Yeah, I wasn't saving either, it's a bit wierd that LUA errors can occur even when you haven't saved the file yet. Maybe some workaround, like adding -- to the front of the line before doing other changes could avoid the problem Quote ■ Ryzen 9 ■ RX 6800M ■ 16GB ■ XF8 ■ Windows 11 ■ ■ Ultra ■ LE 2.5 ■ 3DWS 5.6 ■ Reaper ■ C/C++ ■ C# ■ Fortran 2008 ■ Story ■ ■ Homepage: https://canardia.com ■
Rick Posted January 7, 2010 Author Posted January 7, 2010 That's why I'm not thinking it's a lua error. I think it's an editor error. Quote
Canardia Posted January 7, 2010 Posted January 7, 2010 Yeah, that would make sense, since I don't usually make errors, and I still get those messages. LUA errors show up also differently, with a clear line number and descriptive syntax error. I think the access violation is just a simple memory violation caused by the memory allocation routine of the built-in script editor. Quote ■ Ryzen 9 ■ RX 6800M ■ 16GB ■ XF8 ■ Windows 11 ■ ■ Ultra ■ LE 2.5 ■ 3DWS 5.6 ■ Reaper ■ C/C++ ■ C# ■ Fortran 2008 ■ Story ■ ■ Homepage: https://canardia.com ■
AggrorJorn Posted January 7, 2010 Posted January 7, 2010 Yeah, that would make sense, since I don't usually make errors, unfortunately, I make a lot of errors. Although these are LUA errors, it's still frustating that the entire engine crashes. Quote
Paul Thomas Posted February 7, 2010 Posted February 7, 2010 This is sort of an old post but I get this type of error all the time. Once it happened when I loaded the editor for the first time, as well as the script editor, hit tab, and I got the error. I don't think it's a Lua error. Not exactly sure what it is, but I'm going to switch over to Notepad++ until anything with this is fixed. I also tried the in-editor and standalone Lua editor, both do this, computer specs are always in my signature (Windows XP): Quote
wh1sp3r Posted February 7, 2010 Posted February 7, 2010 i have win7 and this error drive me mad too ,lol it crashes whole editor ! Quote -= Phenom II X4 965 3.4Ghz - ATI HD5870 - 6 GB DDR3 RAM - Windows 8 Pro 64x=- Website: http://www.flamewarestudios.com
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.