Advanced .NET Debugging Techniques from a Real-World Investigation – Webinar Recording

The recording of our September 25th webinar featuring Christophe Nasarre and Kevin Gosse is now available.

You know how it feels. After releasing a new version, a service starts behaving in an unexpected way, and it’s up to you to save the day. But where to start? Criteo processes 150 billion requests per day, across more than 4,000 front-end servers. As part of the Criteo Performance team, our job is to investigate critical issues in this kind of environment.

In this talk, you will follow our insights, mistakes and false leads during a real world case. We will cover all the phases of the investigation, from the early detection to the actual fix, and we will detail our tricks and tools along the way.

Resources shared by Christophe and Kevin:

Subscribe to our community newsletter to receive notifications about future webinars.

This entry was posted in How-To's and tagged , , , , , . Bookmark the permalink.

9 Responses to Advanced .NET Debugging Techniques from a Real-World Investigation – Webinar Recording

  1. Pingback: Dew Drop - September 27, 2018 (#2812) - Morning Dew

  2. Markus says:

    Thanks for this very interesting webinar!
    Is it possible to get the source code of this small “FindTimers” project you showed in the webinar?

    Thanks and Regards,
    Markus

  3. Pingback: The Morning Brew - Chris Alcock » The Morning Brew #2674

  4. D.R. says:

    Very interesting stuff! Hope you’re going to do more, or create a series out of this!

  5. Pingback: Dew Drop - September 28, 2018 (#2813) - Morning Dew

  6. Alex says:

    Thanks for the great webinar!

    I also faced the bug with the infinite ThreadAbortException in my project and also tried to figure out why it happened. However gave up due to luck of time and it was one of the mysteries I lived with :) Great that you finally found out the culprit. Could you please share a link to the bug you registered?

    Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *