SASL insufficient memory crash
Posted: Sun Jul 30, 2017 8:06 amI posted this on the X-Plane and Aerobask forums to see if anyone else is experiencing this or has any suggestions on what I should try next. I really like the Skyview avionics interface because I have found it to be the easiest to manipulate in the VR environment with the mouse while using the HMD. I would love to get this issue resolved but I cannot thing of anything else to try. I will attach my log text file as soon as I get back to my sim computer. Or, here is a link to the x-plane forum post with the attachment : http://forums.x-plane.org/index.php?/fo ... emory-ctd/
I am experiencing a consistent " X-Plane stopped working" message, always occurring after about 5 minutes of flight in the latest ver. Aerobask Eclipse NG and Epic 1000, both using the "Skyview" avionics and XP 11.05. The last line of the attached X-Plane txt.log file reads " (SASL ERROR) Error updating avionics: not enough memory" . These are the only airplanes that I am experiencing this problem with. I posted this over on the Aerobask manufacturers support thread and a forum member directed me to another thread where this issue was being discussed. One of the Aerobask devs posted this comment: " We read apt.dat files for retrieving COM frequencies and the one for prefab 1 is too big: despite we read it line by line, it triggers a memory request bigger than 32 MB in one shot that X-Plane cannot handle properly. Note that other plugins can also interfere, especially Gizmo which also uses lua memory. SASL alone should stop immediately when it happens but there's a bug in XP that makes it crash later instead." I am not using the Prefab 1 plugin orr LUA and I have tried removing all plugins including Gizmo, except SASL but I am still experiencing the crashes. I am using Fly Inside with Oculus, Win 7, i7 4700 @ 4K , 16gig sys ram, Zotec GTX 1070 GPU. The strange thing is, I have not always had these issues with the Skyview avionics. I usually fly over regions where I have orthoXP's. It doesn't seem to matter if I fly VFR or with a flight plan in the FMS. The same is true whether I fly in a densely populated area or in a remote setting. The only thing that I can think of that changed a few days before these crashes started was an NVidia driver update released mid May. They have released another one since then, to which I have updated but the problem persists. I am also using the latest ver. of SKYMAX Pro but the problem persists when I disable this with the other plugins- Autogate, EZ Pushback, RealWeather Connector, Silverlining, x737xpl and XSquawkbox. Any suggestions?
Thanks!
I am experiencing a consistent " X-Plane stopped working" message, always occurring after about 5 minutes of flight in the latest ver. Aerobask Eclipse NG and Epic 1000, both using the "Skyview" avionics and XP 11.05. The last line of the attached X-Plane txt.log file reads " (SASL ERROR) Error updating avionics: not enough memory" . These are the only airplanes that I am experiencing this problem with. I posted this over on the Aerobask manufacturers support thread and a forum member directed me to another thread where this issue was being discussed. One of the Aerobask devs posted this comment: " We read apt.dat files for retrieving COM frequencies and the one for prefab 1 is too big: despite we read it line by line, it triggers a memory request bigger than 32 MB in one shot that X-Plane cannot handle properly. Note that other plugins can also interfere, especially Gizmo which also uses lua memory. SASL alone should stop immediately when it happens but there's a bug in XP that makes it crash later instead." I am not using the Prefab 1 plugin orr LUA and I have tried removing all plugins including Gizmo, except SASL but I am still experiencing the crashes. I am using Fly Inside with Oculus, Win 7, i7 4700 @ 4K , 16gig sys ram, Zotec GTX 1070 GPU. The strange thing is, I have not always had these issues with the Skyview avionics. I usually fly over regions where I have orthoXP's. It doesn't seem to matter if I fly VFR or with a flight plan in the FMS. The same is true whether I fly in a densely populated area or in a remote setting. The only thing that I can think of that changed a few days before these crashes started was an NVidia driver update released mid May. They have released another one since then, to which I have updated but the problem persists. I am also using the latest ver. of SKYMAX Pro but the problem persists when I disable this with the other plugins- Autogate, EZ Pushback, RealWeather Connector, Silverlining, x737xpl and XSquawkbox. Any suggestions?
Thanks!
Even at only 16 Gig, I don't think I am hitting the wall with my sys memory. If this SASL memeory conflict is is an issue being worked on I'll just wait it out but I sure hate to leave my Aerobask planes in sitting the hanger while I wait!