12 Replies Latest reply on Mar 8, 2011 3:20 PM by Flex harUI

    Any ETA on fixing the profiler?

    tehxike1 Level 1

      I've had a lot of problems in the past with crashing, memory leaks, and sluggishness in the past with the profiler.  Now on one of my projects, my application simply freezes up at an early stage when profiling, regardless of the computer I use to profile.

       

      Are there any patches planned soon that will make the profiler more usable?  I'm trying to troubleshoot a bizarre lag issue with my application, and really don't know how to do do it without the profiler's help.

        • 1. Re: Any ETA on fixing the profiler?
          Flex harUI Adobe Employee

          The 4.5 Profiler should be a little faster and better, but nothing will help

          more than making sure your application is properly modular and scaleable.

          • 2. Re: Any ETA on fixing the profiler?
            tehxike1 Level 1

            Yes, my problems have frequently been with large projects, but in this case it's a very small project, which references two library projects.

            • 3. Re: Any ETA on fixing the profiler?
              jfairley2

              I have tried to use "report abuse" but I received an "unexpected error" in response, so I will report my comment here:

              tehxike1's request is valid. The Flash Builder profiler commonly hogs up more resources than Flash Builder is allowed to dole out (probably due to the Java memory allotments).

               

              More importantly, it was very unprofessional of "Flex harUI" to question the quality of tehxike1's code in his response. The sole purpose of a profiler is to find and correct issues. The fact that he is using the profiler means that tehxike1 is actively trying to improve his code. If every application was written to be "properly modular and scaleable" we would have no use for a profiler in the first place.

              Such responses from an Adobe employee are unacceptable and reflect poorly on Adobe as a whole

              • 4. Re: Any ETA on fixing the profiler?
                pauland Level 4

                jfairley2 wrote:

                 

                I have tried to use "report abuse" but I received an "unexpected error" in response, so I will report my comment here:

                 

                tehxike1's request is valid. The Flash Builder profiler commonly hogs up more resources than Flash Builder is allowed to dole out (probably due to the Java memory allotments).

                 

                More importantly, it was very unprofessional of "Flex harUI" to question the quality of tehxike1's code in his response. The sole purpose of a profiler is to find and correct issues. The fact that he is using the profiler means that tehxike1 is actively trying to improve his code. If every application was written to be "properly modular and scaleable" we would have no use for a profiler in the first place.

                Such responses from an Adobe employee are unacceptable and reflect poorly on Adobe as a whole

                 

                You'll need to grow a thicker skin if you think Flex harUI was abusive and unprofessional. Given the way people frequently code projects it was a perfectly reasonable point to make. Simply good advise, not critical or abusive.

                • 5. Re: Any ETA on fixing the profiler?
                  jfairley2 Level 1

                  Give me a break. I'm not offended. I just thought it was unprofessional.

                  • 6. Re: Any ETA on fixing the profiler?
                    pauland Level 4

                    I don't know where the offended bit comes from. I've worked with some people who certainly specialised in abusive unpofessional and nothing in this thread is anywhere close, just friendly advice.

                    • 7. Re: Any ETA on fixing the profiler?
                      jfairley2 Level 1

                      "thick-skinned" == "not easily offended"

                       

                      http://www.thefreedictionary.com/thick-skinned

                      • 8. Re: Any ETA on fixing the profiler?
                        Flex harUI Adobe Employee

                        If you can, file a bug with your project and library projects.

                         

                        If you turn off memory profiling, does the profiler run better?  It should

                        still show you the big time consumers in your app.  And if it makes a

                        difference, there might simply be too much memory allocation going on.

                        • 9. Re: Any ETA on fixing the profiler?
                          Flex harUI Adobe Employee

                          His request is absolutely valid.  We all wish the profiler ran faster.

                          However, it doesn't and order of magnitude improvements aren't likely for

                          4.5.  Given that, it is important to be able to keep parts of your app from

                          running when profiling so there is less data to munch.  A good modular and

                          scalable design makes that easier, and will likely solve lots of other

                          issues going forward.

                           

                          I'm sorry you felt my response was unprofessional.

                          • 10. Re: Any ETA on fixing the profiler?
                            tehxike1 Level 1

                            If you can, file a bug with your project and library projects.


                            If you turn off memory profiling, does the profiler run better?  It should

                            still show you the big time consumers in your app.  And if it makes a

                            difference, there might simply be too much memory allocation going on.

                             

                            Sorry- should have mentioned that.  That's one of the first things I tried- I'm exclusively using performance profiling.  Memory profiling does work, but I don't get any good clues from it.  Not sure what to do as far as filing a bug- I can't submit the source for any of these projects.

                            • 11. Re: Any ETA on fixing the profiler?
                              pauland Level 4

                              jfairley2 wrote:

                               

                              "thick-skinned" == "not easily offended"

                               

                              http://www.thefreedictionary.com/thick-skinned

                               

                              Threads always go downhill when the dictionary comes out. I think we're done.

                              • 12. Re: Any ETA on fixing the profiler?
                                Flex harUI Adobe Employee

                                When you say "freezes", what does that really mean?  If you wait five

                                minutes, does something eventually happen, does the player time out, or

                                something else?

                                 

                                I assume if you don't run the profiler and just run it in the debugger that

                                the app starts up?

                                 

                                I think this is when I would start commenting out code.  If you comment out

                                a bunch of UI and suddenly it runs better, it tells you where to look next.

                                That's how we did it before we had a profiler.  Hopefully your app is

                                written in a way that commenting out sections doesn't result in lots of

                                gluing back together.