#63 100% with Large Module Files


When using a large module, it does not open correctly using the File>>Open Module mechanism. Gpredict consumes 100% of the CPU.

The same module may work when being opened when the program starts but it does not work when opened from the menu or after being edited with the configuration dialog.

A sample module is attached. It is based on the cosmos 2251 debris tle from celestrak. <http://celestrak.com/NORAD/elements/cosmos-2251-debris.txt>.


  • Charles Suprin

    Charles Suprin - 2011-07-02

    Cosmos 2251 debris file

  • Alexandru Csete

    Alexandru Csete - 2011-07-02

    This one never gets old...
    The user manual recommends up to 10-15 satellites per module, see page 17.

  • Charles Suprin

    Charles Suprin - 2011-07-04

    Understood about the file size.

    What bothers me more is that the file loads differently depending on whether it is loaded at startup or from the menu. Either should work the same and result in the same behavior.

    Until the behavior is understood, it might apply to normal modules as well.

  • Charles Suprin

    Charles Suprin - 2011-08-21

    This appears to be triggered by the presence of a polar view in the module. Eliminating the polar view seems to fix this.


Log in to post a comment.