<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hello David, in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131663#M16744</link>
    <description>&lt;P&gt;Hello David,&lt;/P&gt;

&lt;P&gt;Is there a chance to get your app to reproduce the issue locally?&lt;/P&gt;

&lt;P&gt;Thanks, Denis&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Sep 2018 07:09:48 GMT</pubDate>
    <dc:creator>Denis_P_Intel</dc:creator>
    <dc:date>2018-09-21T07:09:48Z</dc:date>
    <item>
      <title>Heap corruption when profiling .Net App</title>
      <link>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131662#M16743</link>
      <description>&lt;P&gt;I'm regularly seeing a problem with .Net (C#) apps which run perfectly well outside VTune, but which when I attempt to profile them crash almost immediately with a stack trace in RtlFree and a message of heap corruption.&lt;/P&gt;

&lt;P&gt;Is this a known problem? Is there a workaround?&lt;/P&gt;

&lt;P&gt;This is using Vtune 2018 update 3.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 19 Sep 2018 13:03:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131662#M16743</guid>
      <dc:creator>christensen__david</dc:creator>
      <dc:date>2018-09-19T13:03:56Z</dc:date>
    </item>
    <item>
      <title>Hello David,</title>
      <link>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131663#M16744</link>
      <description>&lt;P&gt;Hello David,&lt;/P&gt;

&lt;P&gt;Is there a chance to get your app to reproduce the issue locally?&lt;/P&gt;

&lt;P&gt;Thanks, Denis&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 07:09:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131663#M16744</guid>
      <dc:creator>Denis_P_Intel</dc:creator>
      <dc:date>2018-09-21T07:09:48Z</dc:date>
    </item>
    <item>
      <title>The full app is commercially</title>
      <link>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131664#M16745</link>
      <description>&lt;P&gt;The full app is commercially sensitive, but I'll try to produce a cut-down version that exhibits the problem.&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;

&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Mon, 24 Sep 2018 12:02:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131664#M16745</guid>
      <dc:creator>christensen__david</dc:creator>
      <dc:date>2018-09-24T12:02:25Z</dc:date>
    </item>
    <item>
      <title>If it helps, here's the call</title>
      <link>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131665#M16746</link>
      <description>&lt;P&gt;If it helps, here's the call stack&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="callstack.PNG"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/9953i83BC94A201A22996/image-size/large?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="callstack.PNG" alt="callstack.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Sep 2018 13:19:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Heap-corruption-when-profiling-Net-App/m-p/1131665#M16746</guid>
      <dc:creator>christensen__david</dc:creator>
      <dc:date>2018-09-24T13:19:13Z</dc:date>
    </item>
  </channel>
</rss>

