Skip navigation
Currently Being Moderated

4.7 is good, but _SLOW_!

Dec 11, 2012 8:38 AM

Tags: #slow #4.7

Is it just me, or does FB 4.7 hang after about an hour and a half of serious coding?

 

When I fire it up, it runs sweetly and has lots of nice features, but after a bit of work, I find it can take twenty seconds or more _just_to_type_and_see_a_character_on_the_screen_!

 

That is _really_ irritating and only rectifies with a restart of FB.

 

There has to be a better way.

G

 
Replies
  • Currently Being Moderated
    Dec 12, 2012 10:12 AM   in reply to Gaius Coffey

    Hi Gaius,

     

    Couple of questions, answers to which would help us resolve your issue better :

     

    1. Are you on Flash Builder 32 bit or 64 bit?

    2. Are there multiple projects in your workspace? What would be the size of your projects and the no. of class files?

    3. Is the slowness observed in editor for files of any size or is it a particular file you are facing this issue in?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 13, 2012 12:34 AM   in reply to Gaius Coffey

    Hey Gaius,

     

    Can you send the heap dump just when the editor tends to get slow as you mentioned?

     

    For getting the heap dump, get the PID of FlashBuilder from Task Manager.

    Go to command prompt and change directory to your jdk location > bin folder, (your bin folder would be having jmap.exe)

    Type the below command :

    jmap -dump:format=b,file="C:\heap.txt" <pid>

     

    Send the generated heap.txt file to gkalyaniATadobeDOTcom

     

    For bug https://bugs.adobe.com/jira/browse/FB-35854

    Can you send across the workspace log, located at your <FBWorkspace>/.metadata/.log file to the above mentioned email id?

    Also, do not use an old 4.6 workspace. Create a new one for 4.7 and import the required projects from the old workspace.

     

    Regards,

    Guriya

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 13, 2012 10:37 PM   in reply to Gaius Coffey

    Hi Gaius,

     

    By looking at the log it looks like the project setup is causing this issue.

     

    Can you send us the  .actionScriptProperties file of the project from the FB 4.6 and FB 4.7 workspaces ?

    We would like to analyze the file before (in 4.6) and after import (in 4.7).

     

    Thanks

    Sreenivas

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 14, 2012 3:44 AM   in reply to Gaius Coffey

    Hi Gaius,

     

    The log files and actionScriptFiles seem to indicate the following.

     

    1. FB 4.6 and FB 4.7 have been run pointing to them to same workspace. (The log shows -ws win32 -arch x86_64 and -ws win32 -arch x86)

     

    2. The ini file has been edited to pass some custom options which seem to be -data E:\Slidepath\InternalSVN\FB47_flex or -data E:\tweak\flex in different runs. Does this also mean you have extra plugins which process this information ?

     

    3. Lot of Null pointer exceptions in a gustavo_mobile_module project for Android which seems to suggest the project is corrupted.

     

    4. The latest actionScriptProperties files you have sent are not for the PBWorkspace.log file but a different project.

     

    I think it might be better to have a connect session by which we can actually see the issue happening which will also enable to us to see the different steps you are using while running into this issue.

     

    Please let me know whether you will be able to spare sometime and do a connect session with us.

     

    I am working out of Adobe Bangalore, India office. Please let me know your location and availability so that we can schedule a meeting.

     

    Thanks

    Sreenivas

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 7:53 AM   in reply to Gaius Coffey

    I am having the exact same problems.  I've changed my eclipse.ini file settings per Adobe FB4.7 installation recommendations and still having poor performance.  Having to restart FB4.7 every few minutes.  I've also changed the FlashBuilder.ini file to Xmx2048 and sitll no improvement.

     

    Grateful for any Adobe expert out there who can recommend a fix.  Developing in FB4.7 at this point is useless.

     

    Please help, thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2013 7:58 AM   in reply to Cyclex

    I did just notice something odd.  Looking in the eclipse.ini file I see a reference to the plugins folder:

    --launch library

    plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110 502

     

    Is that correct for a 64 installation for Flash Builder 4.7?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 3:53 AM   in reply to Cyclex

    Hi Cyclex,

     

    we were able to address Gaius issue by tracing it to a cyclic reference of MXML components with events. I don't think the same fix would work for you as he was unable to open a particular MXML file in the IDE.

     

    Can you reproduce the issue you are facing in a simple Flex project or it is happening with a particular project you are working on ?

     

    Would you be able to do a connect session showing this issue ? I am working from Bangalore, India office.

     

    If you can let us know your location and availability we would like to do a connect session and understand the issue better so that we can find a solution.

     

    The win32 plugin is correct for the 64bit installation.

     

    You can mail me at sramaswaATadobeDOTcom

     

    Thanks

    Sreenivas

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2013 6:48 PM   in reply to Sreenivas R

    I can make myself available over the next couple days between 9am and 5pm Mountain Standard Time

     

     

     

    Information contained within this email is confidential and proprietary.  Disclosure is prohibited without consent from Cyclex Solutions or its partners.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2013 8:23 PM   in reply to Cyclex

    Hi,

     

    please send a mail to sramaswaATadobeDOTcom so that I can send you the connect and conferencing details to your personal mail.

     

    I will setup a meeting for Thursday 9 AM your time or Friday 9 AM in case you do not see this in time.

     

    Thanks

    Sreenivas

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2013 12:08 AM   in reply to Gaius Coffey

    Hi there

    I had the same issue: the MXML-Editor crashed when opening MXML files. To be more specific, this was the behavior:

    1) Switch to new (empty) workspace exclusively used by FB4.7

    2) Create new Mobile Project and create/edit new MXML ==> worked

    3) import Project from Harddrive (which was created with FB4.7) with only a very basic MXML ==> worked

    4) import Project from Harddrive (which was created with FB4.7) which contained at least one MXML with a namespace reference to another Project ==> DID NOT WORK

     

    I reproduced this by creating a new Project as described in Step 2. MXML editing worked fine. Then I imported the MXML-File with the "wrong" namespace attribute ("xmlns:s="path.from.some.other.project"). From then on, MXML was not possible anymore with ANY of the MXML-Files.

    I then edited the said MXML file by removing the "wrong" namespace and everything worked fine again.

     

    I noticed this because I wanted to use a specific MXML file from another project and just copied it to the new project.To me it seemed as if the namespace makes the editor crash.

     

    This is definitely a bug that has to be fixed by Adobe, since wrong MXML-Tags should not be a problem for the IDE!

     

    Don't know if you guys have the same preconditions, but maybe it works in your case too...

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2013 12:30 AM   in reply to tiefenauer83

    OK, I think I found the bug: I had an MXML called MobileIconItemRenderer.mxml. The Component included another component of the same type. When using this file, the MXML-Editor crashes. However, when you change the tag <renderer:MobileIconItemRenderer> to some other component, it works again!

     

    To me it seems as if the editor can not cope with recursively nested MXML-Components!

     

    <?xml version="1.0" encoding="utf-8"?>

    <s:ItemRenderer xmlns:fx="http://ns.adobe.com/mxml/2009"

                                                      xmlns:s="library://ns.adobe.com/flex/spark"

                                                      initialize="onInitialize(event)"

                                                      width="100%" xmlns:renderer="ch.clx.igh.dataselect.puremvc.view.utils.list.rendere r.*"

                                                      >

     

              <fx:Script>

                        <![CDATA[

                                  import mx.events.FlexEvent;

     

                                  import ch.clx.igh.dataselect.puremvc.view.utils.list.MobileList;

     

                                  public static const NAME:String = "MobileListIconItemRenderer";

                                  //-----------------------------------

                                  // Event names

                                  //-----------------------------------

                                  public static const SHOW_CALLOUT:String = NAME + "ShowCallout";

     

                                  //-----------------------------------

                                  // private variables

                                  //-----------------------------------

                                  private var _calloutTimer:Timer = new Timer(700);

     

                                  //-----------------------------------

                                  // Event Handlers

                                  //-----------------------------------

                                  protected function onInitialize(event:FlexEvent):void{

                                            Multitouch.inputMode = MultitouchInputMode.TOUCH_POINT;

                                            addEventListener(MouseEvent.RIGHT_MOUSE_DOWN, onTouchBegin);

                                            addEventListener(MouseEvent.RIGHT_MOUSE_UP, onTouchEnd);

                                            addEventListener(TouchEvent.TOUCH_BEGIN, onTouchBegin);

                                            addEventListener(TouchEvent.TOUCH_END, onTouchEnd);

                                            _calloutTimer.addEventListener(TimerEvent.TIMER, onCalloutTimer);

                                  }

                                  protected function onTouchBegin(event:Event):void {

                                            _calloutTimer.start();

                                  }

                                  protected function onTouchEnd(event:Event):void{

                                            _calloutTimer.stop();

                                            _calloutTimer.reset();

                                  }

                                  protected function onCalloutTimer(event:TimerEvent):void {

                                            _calloutTimer.stop();

                                            _calloutTimer.reset();

                                            dispatchEvent(new Event(MobileList.SHOW_CALLOUT, true));

                                  }

     

                        ]]>

              </fx:Script>

     

              <s:Image source="{CatalogeView.icons_detail}"

                                   height="100%"

                                   x="10"

                                   focusRect="true"

                                   click="onImageClick(event)"

                                   />

              <renderer:MobileIconItemRenderer id="renderer"

                                                                                                data="{this.data}"

                                                                                                styleName="catologeItem"

                                                                                                decorator="{CatalogeView.pic_arrow}"

                                                                                                width="100%"

                                                                                                height="65"

                                                                                                label="{data.j+': '+data.d}"

                                                                                                iconScaleMode="letterbox"

                                                                                                />

    </s:ItemRenderer>

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 24, 2014 4:17 AM   in reply to tiefenauer83

    Is there any chance for that fix that Sreenivas received? I think I've bumped into the very same issue. I can see that someone posted the file here - http://cloudoflakitu.blogspot.com/2013/11/flash-builder-47-freezes-ope ning-mxml.html, but it's long gone.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points