ephendi

Crash 32bit CRJ-200 XP10

8 posts in this topic

Hello,

there is crash but by log  probably is not memory problem. It's plugin? Last X-aviation version CRJ (32bit still). XP10.20r3 final. MacOSX Mountain Lion. 

Have you got a copy of the Log.txt file as well? And what were you doing just before the CRASH? Had you recently updated/changed anything? Did the CRJ work ok before?

cessna729.

0

Share this post


Link to post
Share on other sites

So log.txt is gone :( . This was only short flight aroud LZIB airport. After final try to go/ around. No "special" operations. And yes, some problems with CRJ exists. When from CRJ200 i want to change aircraft to other, x-plane crash. Only possibility is restart x-plane in 64 bits and change aircraft, and restart back to 32 bit. I will wait for new version of CRJ. All other airplanes with updates sasl works better as before, but x-aviation is too slow with update after x-plane.org. :)

0

Share this post


Link to post
Share on other sites

According to the crash log, this crash has nothing to do with the CRJ at all. It is a plugin crashing on startup, that lives in the namespace "X52", which makes me think it is for the Saitek X52 joystick:

 

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           0000000000 0 + 0
1   libunwind.dylib               0x99e9bed6 unw_get_proc_info + 25
2   libunwind.dylib               0x99e9bf07 _Unwind_GetLanguageSpecificData + 24
3   libc++abi.dylib               0x94ee3b62 __gxx_personality_v0 + 198
4   mac.xpl                       0x1f55d9e6 _Unwind_RaiseException_Phase2 + 102
5   mac.xpl                       0x1f55daad _Unwind_Resume + 109
6   mac.xpl                       0x1f554bdb x52datasource_t::x52datasource_t(char const*) + 315
7   mac.xpl                       0x1f554cd3 x52data_t::add_datasource(char const*) + 67
8   mac.xpl                       0x1f559f26 x52time_t::set_datasources(std::map<int, std::string, std::less<int>, std::allocator<std::pair<int const, std::string> > >*) + 118
9   mac.xpl                       0x1f55a907 x52time_t::x52time_t(char const*, x52out_t*, x52data_t*) + 983
10  mac.xpl                       0x1f552372 x52session_t::create_defaultpages() + 306
11  mac.xpl                       0x1f55254d x52session_t::x52session_t() + 141
12  mac.xpl                       0x1f5520fe XPluginStart + 222
13  XPLM                           0x1f36b902 LoadOnePlugin(std::string const&, int) + 506
14  XPLM                           0x1f36bd87 LoadFatPlugin(std::string const&) + 115
15  XPLM                           0x1f36c268 XPLMFindAndLoadPlugins(char const*) + 1206
16  XPLM                           0x1f36a311 XPLMInitializePlugins + 169
17  com.laminar_research.X-Plane   0x0086b6dd XPPInitializePlugins(char const*) + 3501
18  com.laminar_research.X-Plane   0x00440a1d MACIBM_init(int, char const* const*) + 10957
19  com.laminar_research.X-Plane   0x0057cccb init_sim(int, char const* const*) + 27
20  com.laminar_research.X-Plane   0x0057d55b main + 43
21  com.laminar_research.X-Plane   0x003f6f39 start + 53
0

Share this post


Link to post
Share on other sites

According to the crash log, this crash has nothing to do with the CRJ at all. It is a plugin crashing on startup, that lives in the namespace "X52", which makes me think it is for the Saitek X52 joystick:

 

Interresting, this not happend with any other airplane only with CRJ200 :(... aaaand today same problem with CRJ200 with no saitek x52 plugged into my mac. 

Edited by ephendi
0

Share this post


Link to post
Share on other sites

@ephendi

Attach a copy of you latest Crash log and log.txt to check if it still is related. :)

Were you flying in the same area/scenery as before? If so what happens when you fly somewhere different?

cessna729.

0

Share this post


Link to post
Share on other sites

Interresting, this not happend with any other airplane only with CRJ200 :(... aaaand today same problem with CRJ200 with no saitek x52 plugged into my mac. 

 

It doesn't make any change whether the joystick is plugged in, it is about the X52 plugin being loaded.

The X52 plugin would not be the first one to to exhibit errors when used in conjunction with the CRJ, just remember the XPUIPC plugin. The crash report speaks a very clear language: The X52 plugin crashed.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.