LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  BRE taking 5+ minutes to open

    Employee
    Posted 08-26-2014 08:03

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: gauravdb

    Hi guys,

    I am facing a really awkward problem from few days. If I open BRE(even a new/blank), it is taking too long, about 5-7 minutes to open the graph.

    Anyone can help on this issue please ? Is there something wrong with my settings ?

    Thanks
    GK


  • 2.  RE: BRE taking 5+ minutes to open

    Employee
    Posted 08-26-2014 08:20

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Tim Meagher

    This could be due to a number of reasons, however often when I see this it's because of bad search path settings.
    Within BRE, go to Tools->Preferences->Search paths and check the settings there.
    Whenever starting BRE, it will create a new graph and load up the base libraries to display the palette.
    By default, these libraries are core, inFlow, and then libraries you have setup in the default base libraries.
    However, the base libraries do not point to a specific library (BRG) - rather they point to the name of the library.
    BRE will then search first in the location of the current BRG (if opening an existing BRG), then will search in order in each of the directories specified in the search paths recursively in order to try and locate the libraries.

    If you have something like C:\ in your search paths (or any directory which contains a lot of files/subfolders) then this initial search for base libraries can take a very long time.
    It is best to remove such entries - at the very least, they should come after the <BRE Install Directory>/lib/brain/brg directory.

    Hope this helps.
    If this isn't the problem, then post back.
    It could be something else is wrong with the setup or might be something that you need to contact support about.

    Regards,
    Tim.