TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 - CTD

[WaarEagle]

After making several test flights, I'm 99.9% sure that (in my situation) the conflict is occurring between the TBM and ActiveSky.  I tried a flight with World Traffic 3 disabled and experienced a crash within 30 minutes.  For the next flight, I re-enabled World Traffic and changed the weather generation from ActiveSky to X-Plane's internal real-world weather. Since then, I have not had any crashes at all.

Based on reports from other users, I'm not inclined to believe that the problem is caused exclusively by ActiveSky (since others are experiencing the occasional exception handler fault with xEnviro, FSGRW, XSquawkbox, etc.). Again, my gut tells me that the TBM is not correctly handling certain weather changes initiated by external weather programs... but I'm not sure which parameter (wind, cloud cover, precip?) is the cause.  I remember that several builds back, the TBM was crashing consistently for everyone after Laminar made some weather-related code changes in 11.31.  That problem has obviously been resolved; but I'm beginning to wonder if this is a very similar issue - except that it only occurs when using external weather generators.

To add additional detail, I normally run Activesky on a remote computer.  The program communicates with X-Plane over a network using the ASXPConnect plugin.  I have NOT disabled the plugin in X-Plane; so the TBM and ASXPConnect module do not appear to conflict unless ActiveSky is "actively" manipulating the weather.  I hope this provides some clues on where to start looking to resolve this issue.

Edited April 28, 2019 by WaarEagle

[Goran_M]

@skiselkov

[bunchy]

Hi Goran,

I'm getting these exception handler problems too.

They are quite intermittent for me, about once every three flights. Just before the crash, my sound goes off for a second, then recovers for about 2 seconds, then a CTD.

I run Ortho for pretty much all of Europe, the latest crash was flying from Rhodes to Florence.

My Plugin folder content image is attached.

The strange thing is, 66% of the time, I have no problems.

I use consistently, with every XP flight, the following:

ASXP, EFBv2, ProjectFly.

Sometimes, as an alternative to EFBv2, I use Navigraph's simconnect. Never at the same time though. If I'm not using Navigraph's simconnect, I uninstall the plugin.

 

Hope this helps

 

Stu

Log.txt

TBM900_Log.txt

[AgeHawk]

I purchased the TBM900 a day or two and was able to fly it for some hours but now it keeps crashing my XP11. At least 4 times now in 4 flights one of which only lasted some seconds. I have read through the forum, I don't think anyone should uninstall any product just to get this thing working. The should and must have to find wherever the exception is being thrown and handle the issue there. Instead of causing XP to crash.

Here is the message:  TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000.

We should stop blaming other products. I don't use any environment software and all aircraft  I have so far don't have this issue. I use airfoillabs and no such issue, they should fix it as soon as possible.

[Goran_M]

We can't help but to blame other software.  The TBM runs flawlessly on most peoples setups.  There are a handful of people who are experiencing this particular problem, and it is down to a conflict between the TBM and a slightly buggy plugin.  Other aircraft don't have this issue because other aircraft either don't use a TCAS or use a very basic version of one.  The TCAS in the TBM is very complex.
In your case, even without a log file, I'm going to ask, are you running LiveTraffic or any other kind of traffic plugin?  If the answer is yes, then the problem is easily diagnosed, and a fix is easily implemented on the users end.  

Edited October 10, 2019 by Goran_M

[Ben Russell]

10 hours ago, aegiomo@gmx.de said:

I purchased the TBM900 a day or two and was able to fly it for some hours but now it keeps crashing my XP11. At least 4 times now in 4 flights one of which only lasted some seconds. I have read through the forum, I don't think anyone should uninstall any product just to get this thing working. The should and must have to find wherever the exception is being thrown and handle the issue there. Instead of causing XP to crash.

Here is the message:  TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000.

We should stop blaming other products. I don't use any environment software and all aircraft  I have so far don't have this issue. I use airfoillabs and no such issue, they should fix it as soon as possible.

X-Plane doesn't have memory protection between plugins.

It is like using Windows 3.x or Mac OS Classic in this regard.

If you look into the history of these OS's it was very common for bugs and system crashes to occur because there was no memory protection and a fault in one app could overwrite the memory of another leading to undefined behaviour.

 

This is no longer an issue with a modern OS however X-Plane and its plugin sub-system is NOT a modern OS and has no memory protection by default.

[AgeHawk]

@Goran_M Thank you very much for the reply and suggestion. I use LiveTraffic and removed it. After that, it went well and did not have any other issues but the next day, after loading the aircraft I then started LittleNavMap so I can create a flight plan, X-Plane crashed immediately. I then repeated the same process but this time opened the SimToolKitPro so I can create a flight plan, an again X-Plane crashed. I did it twice with the two application (4x), X-Plane crashed at every instance. The most frustrating thing is crashing X-Plane which takes very long to load if you know what I mean. It doesn't crash if I just go ahead and fly the plane without these tools - I have not tried it with X-Life. I have been using these tools without issues but they all seem to have problems with PBM9000.

@Ben Russell That explains everything. All the applications running under windows seem to inherit this pattern but I see it as something they should work on, just tired of all crashes in windows and applications. The host should catch any uncaught exception and destroy the culprit.

[AgeHawk]

Ok. I just started it without any tool but still I get this error below. 

 

2019-10-12 20:29:06 TBM900[xplane.c:1160]: This is the TBM900 (v1.1.9) libacfutils-62765a8
2019-10-12 20:29:06 TBM900[xplane.c:1205]: BOOT: glew_init
2019-10-12 20:29:06 TBM900[xplane.c:1219]: BOOT: glutils_sys_init
2019-10-12 20:29:06 TBM900[xplane.c:1221]: BOOT: lr_init
2019-10-12 20:29:06 TBM900[xplane.c:1223]: BOOT: gl_pic_sys_init
2019-10-12 20:29:06 TBM900[xplane.c:1226]: BOOT: acf_mgr_init
2019-10-12 20:29:06 TBM900[xplane.c:1234]: BOOT: updater_init
2019-10-12 20:29:06 TBM900[xplane.c:1237]: Systems plugin load complete
2019-10-12 20:29:07 TBM900[xplane.c:1299]: Systems plugin is enabling
2019-10-12 20:29:07 TBM900[xplane.c:1303]: BOOT: mtcr_glob_init
2019-10-12 20:29:07 TBM900[xplane.c:1310]: BOOT: fontmgr_init
2019-10-12 20:29:07 TBM900[xplane.c:1313]: BOOT: pulldown_init
2019-10-12 20:29:07 TBM900[xplane.c:1315]: BOOT: efis_widget_sys_init
2019-10-12 20:29:07 TBM900[xplane.c:1317]: BOOT: util_init
2019-10-12 20:29:07 TBM900[xplane.c:1321]: BOOT: sys_disp_glob_init
2019-10-12 20:29:07 TBM900[xplane.c:1323]: BOOT: scr_cap_init
2019-10-12 20:29:07 TBM900[xplane.c:1326]: BOOT: fail_init
2019-10-12 20:29:07 TBM900[xplane.c:1328]: BOOT: seats_init
2019-10-12 20:29:07 TBM900[xplane.c:1331]: BOOT: cas_init
2019-10-12 20:29:07 TBM900[xplane.c:1333]: BOOT: airframe_init
2019-10-12 20:29:07 TBM900[xplane.c:1335]: BOOT: doors_init
2019-10-12 20:29:07 TBM900[xplane.c:1337]: BOOT: gse_init
2019-10-12 20:29:07 TBM900[xplane.c:1339]: BOOT: sensors_init
2019-10-12 20:29:07 TBM900[xplane.c:1341]: BOOT: gear_init
2019-10-12 20:29:07 TBM900[xplane.c:1344]: BOOT: elec_init
2019-10-12 20:29:07 TBM900[xplane.c:1347]: BOOT: engine_init
2019-10-12 20:29:07 TBM900[xplane.c:1350]: BOOT: fms_init
2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 1053

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2005

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2016

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2048

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2098

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2186

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2867

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3332

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4623

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5572

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5583

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5614

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5665

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5751

2019-10-12 20:29:07 TBM900[navaiddb.c:512]: Error parsing D:\SteamLibrary\steamapps\common\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6434

2019-10-12 20:29:07 TBM900[xplane.c:1353]: BOOT: fuel_init
2019-10-12 20:29:07 TBM900[xplane.c:1355]: BOOT: ecs_init
2019-10-12 20:29:07 TBM900[xplane.c:1358]: BOOT: ap_init
2019-10-12 20:29:07 TBM900[xplane.c:1360]: BOOT: adc_init
2019-10-12 20:29:07 TBM900[xplane.c:1362]: BOOT: ckpt_anim_init
2019-10-12 20:29:07 TBM900[xplane.c:1364]: BOOT: reg_init
2019-10-12 20:29:07 TBM900[xplane.c:1366]: BOOT: effects_init
2019-10-12 20:29:08 TBM900[xplane.c:1369]: BOOT: ice_init
2019-10-12 20:29:08 TBM900[xplane.c:1373]: BOOT: snd_sys_init
2019-10-12 20:29:08 TBM900[xplane.c:1377]: BOOT: audio_init
2019-10-12 20:29:08 TBM900[xplane.c:1379]: BOOT: efis_utils_init
2019-10-12 20:29:08 TBM900[xplane.c:1383]: BOOT: efis_sys_init
2019-10-12 20:29:08 TBM900[xplane.c:1387]: BOOT: drawer_init
2019-10-12 20:29:08 TBM900[xplane.c:1391]: BOOT: xp_state_init
2019-10-12 20:29:08 TBM900[xplane.c:1393]: BOOT: maint_init
2019-10-12 20:29:08 TBM900[xplane.c:1396]: BOOT: maintlog_init
2019-10-12 20:29:08 TBM900[xplane.c:1398]: BOOT: taws_init
2019-10-12 20:29:08 TBM900[xplane.c:1401]: BOOT: wxr_init
2019-10-12 20:29:08 TBM900[xplane.c:1404]: BOOT: tas_init
2019-10-12 20:29:08 TBM900[xplane.c:1407]: BOOT: adf_dme_init
2019-10-12 20:29:08 TBM900[xplane.c:1410]: BOOT: efis_init
2019-10-12 20:29:08 TBM900[libsvs.c:4857]: libsvs(PFD): utilizing background rendering via wglCopyImageSubDataNV
2019-10-12 20:29:09 TBM900[xplane.c:1413]: BOOT: tablet_init
2019-10-12 20:29:09 TBM900[libsvs.c:4857]: libsvs(tablet): utilizing background rendering via wglCopyImageSubDataNV
2019-10-12 20:29:09 TBM900[xplane.c:1416]: BOOT: xpdr_init
2019-10-12 20:29:09 TBM900[xplane.c:1418]: BOOT: elt_init
2019-10-12 20:29:09 TBM900[xplane.c:1420]: BOOT: hypoxia_init
2019-10-12 20:29:09 TBM900[xplane.c:1423]: BOOT: notif_init
2019-10-12 20:29:09 TBM900[xplane.c:1426]: BOOT: fctl_init
2019-10-12 20:29:09 TBM900[xplane.c:1428]: BOOT: loadmgr_init
2019-10-12 20:29:09 TBM900[xplane.c:1431]: BOOT: charts_init
2019-10-12 20:29:09 TBM900[helpers.c:1029]: Cannot stat D:\SteamLibrary\steamapps\common\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1910: Access is denied.

2019-10-12 20:29:09 TBM900[xplane.c:1434]: BOOT: chklist_init
2019-10-12 20:29:09 TBM900[xplane.c:1436]: BOOT: flightlog_init
2019-10-12 20:29:09 TBM900[xplane.c:1438]: BOOT: crash_init
2019-10-12 20:29:09 TBM900[xplane.c:1440]: BOOT: mfd_page_ind_init
2019-10-12 20:29:09 TBM900[xplane.c:1442]: BOOT: prp_anim_init
2019-10-12 20:29:09 TBM900[xplane.c:1444]: BOOT: axis_init
2019-10-12 20:29:09 TBM900[xplane.c:1446]: BOOT: hud_init
2019-10-12 20:29:09 TBM900[xplane.c:1450]: BOOT: fail_mgr_init
2019-10-12 20:29:09 TBM900[xplane.c:1453]: BOOT: g1000_popup_init
2019-10-12 20:29:09 TBM900[xplane.c:1456]: BOOT: rand_fail_init
2019-10-12 20:29:09 TBM900[xplane.c:1459]: BOOT: tutorial_init
2019-10-12 20:29:09 TBM900[xplane.c:1462]: BOOT: xplane_fdr_find
2019-10-12 20:29:09 TBM900[xplane.c:1289]: Boot complete
2019-10-12 20:29:09 TBM900[xplane.c:1520]: Systems plugin enable complete
2019-10-12 20:30:02 TBM900[fail.c:932]: Component left wing beacon light has failed due to excessive wear (worn: 100.000000%, slope 1.0). You can prevent this by observing performance limitations and servicing the aircraft regularly in the maintenance hangar.
2019-10-12 20:30:02 TBM900[fail.c:935]: Failure impact: tbm900/failures/lights/left_beacon_light
2019-10-12 20:30:02 TBM900[fail.c:932]: Component right wing beacon light has failed due to excessive wear (worn: 100.000000%, slope 1.0). You can prevent this by observing performance limitations and servicing the aircraft regularly in the maintenance hangar.
2019-10-12 20:30:02 TBM900[fail.c:935]: Failure impact: tbm900/failures/lights/right_beacon_light
2019-10-12 20:30:05 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:06 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:07 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:08 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:09 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

 

I would appreciate any help.

[Goran_M]

We need a full log.txt file.  Also, may I suggest also contacting the developers of the other plugins you are using and sending them the same information.  

These lines are too vague for us to find out exactly what is causing the problem, as they don't state the nature of the problem
2019-10-12 20:30:05 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:06 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:07 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:08 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-10-12 20:30:09 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

and whereas I understand this problem doesn't occur with other add ons, the TBM is extremely complex, and is designed to run without crashing X-Plane in its default state, and no plugins installed.  Introducing 3rd party plugins can cause starnge results with any 3rd party aircraft.  

If the developers of the other plugins can come back to you with some information for us on what to fix in the TBM, then we will definitely do so.  For now, all we know is that any 3rd party traffic plugin, unless configured correctly (you can still run livetraffic, but after making an adjustment) will cause this crash.

[seth]

I had also random crashes with TBM 900

2019-10-22 21:19:13 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

is there any update or fix ?

thanks

 

[Goran_M]

3 hours ago, seth said:

I had also random crashes with TBM 900

2019-10-22 21:19:13 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

is there any update or fix ?

thanks

 

A workaround for now.

 

[seth]

12 hours ago, Goran_M said:

A workaround for now.

 

thanks, but i didnt use Live traffic or any AI , looks like there is a conflict with Active sky

 

 

[Goran_M]

Interesting.  Ok, thanks.

[xpst]

Hi Goran,

Quick question: I understand that since plugins run in the context of the main X-Plane process, it's not recommended that plugins have their own exception handler.

Is it really required by your TBM implementation for any useful function, and if so, why ? Can't you get rid of it (and of the problem) ?

[Goran_M]

It's absolutely not required, and by all means, we can take out the offending plugin.  But we need to know what it is first.  Saso is working diligently to try to narrow it down, but when X-Plane refuses to tell us what it is, it makes it that much harder.  He's already updated a ton of code (due for the next update), and hopefully, the exception handler problem is among those fixes.

[xpst]

> we can take out the offending plugin. 
The plugin is the TBM, isn't it, so that doesn't seem an option  ?
But that exception handler is part of the TBM plugin ( TBM900[except.c:282] ), I hope Saso is starting to get clues !

Do you guys already have a tentative date (ok, just give me a year  ) for the next update ?

Just in :
2019-10-23 18:36:02 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
IVAO was loaded. I wasn't connected to the network/using it. I succeeded in making one flight (30 mins) yesterday. Same flight today with same conditions and settings crashed in flight. They're picking my little pieces out of the hills right now.

Thanks !

Log.txt

[Cameron]

3 hours ago, xpst said:

Do you guys already have a tentative date (ok, just give me a year  ) for the next update ?

We do not have a tentative date for the next update.

[xpst]

> tentative date
OK, I understand, Cameron, thanks.

[robe810106]

Hello everyone,

8 months have passed after my initial post and I am still unable to use the TBM900. I have tried everything, several clean installations, drive changes, everything...
Although the simulation world has a magnificent community and a lot of enthusiasm, this began with a commercial transaction of 60 dollars.

Honestly, I think I should have been refunded when I requested it more than six months ago.

I think it is time to forget about Hot Start TBM, my 60 dollars and X-Aviation forever.

Regards.

Edited December 2, 2019 by robe810106

[Goran_M]

1 hour ago, robe810106 said:

Hello everyone,

8 months have passed after my initial post and I am still unable to use the TBM900. I have tried everything, several clean installations, drive changes, everything...
Although the simulation world has a magnificent community and a lot of enthusiasm, this began with a commercial transaction of 60 dollars.

Honestly, I think I should have been refunded when I requested it more than six months ago.

I think it is time to forget about Hot Start TBM, my 60 dollars and X-Aviation forever.

Regards.

I've responded to several people with the same problem you are having.  The fault does not lie, as far as we know, with the TBM.  So a refund can't be given.  The exception handler problem occurs when you have some kind of AI traffic running.  This is something that needs to be addressed with the World traffic developers because all the TBM is doing is reading traffic.  When the error comes up as it does (something reinstalled our exception handler), that is very likely the traffic program doing something to the TBM and causing a crash.  Not all crashes are caused by the TBM.

For a workaround, please see this post.

 

Edited December 2, 2019 by Goran_M

[robe810106]

Hello Goran,

I have a clean X-Plane installation, nothing installed apart from TBM. AI traffic disabled. But, I'll have another look anyway.

 

Regards.

[okidokki]

For me it is definitely not AI or traffic as I don''t have any of it activated.

Until yesterday I was almost sure that it was related to Real Weather Connector - starting roughly 2 months ago I started from (almost) plain X-Plane to gradually re-activate (i.e. move back to the plugins folder) my handful of plugins in order to track this thing down. The last one remaining was RWC and I didn't have a single CTD during this whole period.

Alas, on my last flight yesterday (basically when I had just decided: maybe the issue was somehow fixed by XP 11.40, let's re-animate RWC)  I had the ominous CTD again. So now I know, it is NOT RWC!

What I did notice I couple of times in the log files, that just before the CTD there would be entries from SkyMaxx Pro updating weather...

Anyhow, I guess I will just live with it as I do get the CTD only very occasionally (1 out of 10-20 or so flights), most of the flights work out as expected.

[Goran_M]

7 hours ago, okidokki said:

For me it is definitely not AI or traffic as I don''t have any of it activated.

Until yesterday I was almost sure that it was related to Real Weather Connector - starting roughly 2 months ago I started from (almost) plain X-Plane to gradually re-activate (i.e. move back to the plugins folder) my handful of plugins in order to track this thing down. The last one remaining was RWC and I didn't have a single CTD during this whole period.

Alas, on my last flight yesterday (basically when I had just decided: maybe the issue was somehow fixed by XP 11.40, let's re-animate RWC)  I had the ominous CTD again. So now I know, it is NOT RWC!

What I did notice I couple of times in the log files, that just before the CTD there would be entries from SkyMaxx Pro updating weather...

Anyhow, I guess I will just live with it as I do get the CTD only very occasionally (1 out of 10-20 or so flights), most of the flights work out as expected.

Can you confirm you don't even have X-Plane's own AI running?  ie.  other aircraft is set to zero.

[okidokki]

9 hours ago, Goran_M said:

Can you confirm you don't even have X-Plane's own AI running?  ie.  other aircraft is set to zero.

Yes, I can confirm that - I tend to find them rather annoying, that's why I have set them to zero even before I even purchased the TBM.

btw, I can really understand that this one is really hard to track down - I am not even able to reproduce the effect on my single machine with a limited amount of plugins. I can live with this happening from time to time.

[Goran_M]

I think this has been addressed in the update, as best as it can be, and it may be fixed.  The update is going through testing and should be out very soon.