Apple Debugging L5 - Memory Graph

Поділитися
Вставка
  • Опубліковано 8 вер 2024
  • How to use the memory graph debugging tool in Xcode to catch retain cycles. For some reason Xcode 10.3 seems to yield indeterminate results if malloc stack logging is enabled. Maybe I'll redo this video when this seems reliable.
    Twitter: / lucasderraugh
    GitHub: github.com/luc...
    Site: appleprog.com

КОМЕНТАРІ • 21

  • @rios6984
    @rios6984 Рік тому

    that moment with implicit self in closure is very insightful, thanks!

  • @priceringo1756
    @priceringo1756 5 років тому +2

    Thank you for this and your recent videos. I appreciate the depth of material, something beyond just an introduction.

    • @AppleProgramming
      @AppleProgramming  5 років тому +2

      Price Ringo This series is intended to be a little advanced. I’m glad you’re finding the content useful.

  • @drkirwin
    @drkirwin 5 років тому +1

    I had no idea Xcode had a thing like this. Thanks!

  • @prayash
    @prayash 4 роки тому +1

    This is incredibly useful. Thank you so much! All your lessons go into the perfect amount of depth.

  • @luizhenriqueramos874
    @luizhenriqueramos874 5 років тому +1

    Nice video by the way, thank you for helping us programming on a MAC.

  • @w0mblemania
    @w0mblemania 5 років тому +1

    This was very well explained. Thank you.

  • @chaoukibencherif9307
    @chaoukibencherif9307 4 роки тому +1

    Thank you for this great video

  • @Andrei_Calazans
    @Andrei_Calazans 4 роки тому

    Thank you very much for this content. I am very impressed with the quality of your videos and how deep your knowledge is. May I ask how you make these videos? What is your approach to them? Do you write a script to follow or just do them from the top of your head?
    Cheers, and keep it up man!

    • @AppleProgramming
      @AppleProgramming  4 роки тому +2

      Andrei Calazans Definitely not just winging it 😅. I write all the code I expect to go through and test it out. I aim to make the code simple but still relatable to a real world example. Then I step through the points of progression and joy them down so I know the main things I want to talk about. I basically make an outline and just make sure I go in order for the topic. Everything I say is not written down though, for better or worse.

    • @asifnoor982
      @asifnoor982 2 роки тому

      @@AppleProgramming I learned so much from your videos and thanks @Andrei asking a very good question. I always wondered how you remember you so much when you explain the concept.

  • @tgsoon2002
    @tgsoon2002 5 років тому +1

    Omg. This might be what I looking for. I have problem with memory leak/object is wong right now and it might save my ass.

  • @DigitalHole
    @DigitalHole 3 роки тому

    Well Explain!

  • @luizhenriqueramos874
    @luizhenriqueramos874 5 років тому

    Could you explain me how to clear the console on Xcode C programming? I'm using system ("clear") but I get "terminals database is inaccessible"

  • @ideluxer
    @ideluxer 4 роки тому

    can you add a video for iOS, I mean, the same close app to release memory without killing the debugger / memory graph

  • @nemya24
    @nemya24 4 роки тому

    hi man nice tutorial i have some issue i have splash VC that still have ref to him from uiwindow but thr dinit function called
    and i realy dont now why its happens please help

    • @AppleProgramming
      @AppleProgramming  4 роки тому

      Splash screen view controllers aren't actually used, it's basically a snapshot of the storyboard and that is it. That's why you can't animate or put custom views in a splash screen. This is the likely reason that the view controller is never even used.

  • @dannylones2159
    @dannylones2159 4 роки тому

    can i like this video twice ?

  • @vindajojo
    @vindajojo 2 роки тому

    What if this is an iOS App, I can't close the App without quitting it to view memory leak

    • @AppleProgramming
      @AppleProgramming  2 роки тому

      You don't need close the application. You can trigger the memory graph at any time while the app is running to grab the current memory graph representation.