Do you have a thought as to why I received the bglmanx.dll crash? I've never had it happen before.
In the last couple of days we found a problem with the *previous* version which now has been fixed, but in the case you would have a crash immediately when starting FSX so, your problem seems entirely different.
A crash 6 hours into the flight can't possibly caused by the Addon Manager, the most likely cause is that you were almost exhausting memory because of a memory leak caused by some other memory-hungry product ( the PMDG forum on Avsim is full of users reporting OOMs with the 777 ) so, it's possible that if the Addon Manager needed a bit of memory from Windows to do something ( but if you were *away* from a an FSDT airport, it doesn't do that ) the memory allocation failed because there was no memory left.
That's the only possible explanation I could give considering it would be basically impossible to replicate that situation.
I'd say that, if you want to do a long flight, you should have PLENTY of spare memory before starting it, and being close to the limit is probably not safe because, along a very long flight, things might be loaded, not always be unloaded (FSX is known to keep handles on files open even for sceneries thousands miles away) so it's best to start with enough headroom, using all possible anti-OOM prevention method that were discussed many times here and on other forums.
