<?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 Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596404#M24688</link>
    <description>&lt;P&gt;Hm...the bug is gone. I cannot reproduce it anymore.&lt;BR /&gt;&lt;BR /&gt;I recalled I added symbols for nvidia recently:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://driver-symbols.nvidia.com/" target="_blank"&gt;https://driver-symbols.nvidia.com/&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;but when I added it back it still does not crash.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Command-line:&amp;nbsp;&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Intel\oneAPI\vtune\2024.0\bin64\vtune" -collect hotspots --app-working-dir=V:\build\product\ -- V:\build\product\bin\RelWithDebInfo\Milo-Product.exe&lt;BR /&gt;&lt;BR /&gt;Not sure what happened, but the crash is not reproducible, I can profile again.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2024 17:07:09 GMT</pubDate>
    <dc:creator>LukasT</dc:creator>
    <dc:date>2024-05-09T17:07:09Z</dc:date>
    <item>
      <title>Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1595694#M24676</link>
      <description>&lt;P&gt;I started to get crashes regularly in phase where VTune tries to resolve symbols.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It happened after I updated my system, so maybe I suspect some conflict within environment.&lt;BR /&gt;&lt;BR /&gt;WHat I tried:&amp;nbsp;&lt;BR /&gt;a) repair and reinstall w_oneapi_vtune_p_2024.1.0.520_offline&lt;/P&gt;&lt;P&gt;b) downgrade VTune to&amp;nbsp;w_oneapi_vtune_p_2024.0.1.13_offline.exe&lt;BR /&gt;&lt;BR /&gt;c) clean up local symbols cache completely (to avoid problems with corrupted symbols)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Nothing helped.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Exception]&lt;BR /&gt;Address: 0x00007ff98b5c19e7&lt;BR /&gt;Code: 0x00000000c0000005&lt;BR /&gt;CrashedPID: 25224&lt;BR /&gt;CrashedTID: 7092&lt;BR /&gt;Description: EXCEPTION_ACCESS_VIOLATION&lt;BR /&gt;Module: amplxe_msdia140.dll&lt;BR /&gt;Product: Intel(R) VTune(TM) Profiler 2024.0.1; 627177&lt;BR /&gt;ReportPath: C:\Users\Lukas\AppData\Local\Temp\amplxe-log-Lukas\2024-05-07-18-38-55-719.vtune-worker.exe\&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;[Process]&lt;BR /&gt;Process Name: vtune-worker.exe&lt;BR /&gt;Virtual Memory Size: 6100240K&lt;BR /&gt;Working Set Size: 1484552K&lt;/P&gt;&lt;P&gt;[Products]&lt;BR /&gt;Package ID: N/A&lt;BR /&gt;Package Contents: Intel(R) VTune(TM) Profiler 2024.0.1&lt;BR /&gt;Build Number: 627177&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[PremortalLog]&lt;BR /&gt;334 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - (outputBag != 0) &amp;amp;&amp;amp; (inputBag != 0) &amp;amp;&amp;amp; !m_ctx.is_null() 'gh2::error::FailedTo.Process.The.Parameter:'&lt;BR /&gt;vcs\cfgmgr2\src\rules.cpp(2020): process&lt;BR /&gt;, at file: vcs\cfgmgr2\src\rules.cpp:2020&lt;BR /&gt;367 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Errors happened during transformation&lt;BR /&gt;367 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - %ThisAnalysisTypeIsNotApplicable&lt;BR /&gt;372 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Errors happened during transformation&lt;BR /&gt;372 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - %ThisAnalysisTypeIsOnlyForLinux&lt;BR /&gt;377 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Errors happened during transformation&lt;BR /&gt;377 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - %ThisAnalysisTypeIsNotApplicable&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuL3SamplerThroughputAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuL3ShaderThroughputAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuL3_BYTE_READAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuL3_BYTE_WRITEAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuUntypedBytesReadAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuUntypedBytesWrittenAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSlmBytesReadAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSlmBytesWrittenAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuTypedBytesReadAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuTypedBytesWrittenAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuGtiReadThroughputAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuGtiWriteThroughputAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuGtiL3ThroughputAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuHOST_TO_GPUMEM_BYTE_READAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuHOST_TO_GPUMEM_BYTE_WRITEAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSYSMEM_BYTE_READAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSYSMEM_BYTE_WRITEAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSTACK_TO_STACK_RECEIVEAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2250 [22232] ERROR cfgmgr &amp;lt;&amp;gt; - Cannot find context value: gpuSTACK_TO_STACK_TRANSMITAbsMaxValue., at file: vcs\cfgmgr2\src\rules.cpp:377&lt;BR /&gt;2251 [22232] ERROR dbinterface &amp;lt;&amp;gt; - addColumnV2(): Can't resolve (gpu_data, __bucket_idx): root table is not valid, at file: vcs\dbinterface1\src\sqlite\query.cpp:308&lt;BR /&gt;2251 [22232] ERROR dbiproviders &amp;lt;&amp;gt; - bucketIdx != dbi1::InvalidColIdx&lt;BR /&gt;vcs\dbiproviders1\src\rule_helpers.cpp(682): call&lt;BR /&gt;, at file: vcs\dbiproviders1\src\rule_helpers.cpp:682&lt;BR /&gt;2899 [22232] ERROR dicerresolver &amp;lt;&amp;gt; - gh2::is_success(err)&lt;BR /&gt;vcs\dicerresolver2\src\impl\resolver_impl.cpp(4593): load_settings&lt;BR /&gt;, at file: vcs\dicerresolver2\src\impl\resolver_impl.cpp:4593&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Any suggestions what could help?&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2024 16:58:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1595694#M24676</guid>
      <dc:creator>LukasT</dc:creator>
      <dc:date>2024-05-07T16:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1595839#M24678</link>
      <description>&lt;P&gt;Could you post the command line and attach the log file?&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 06:31:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1595839#M24678</guid>
      <dc:creator>yuzhang3_intel</dc:creator>
      <dc:date>2024-05-08T06:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596263#M24682</link>
      <description>&lt;P&gt;I execute the Intel VTune directly from MSVC IDE through the UI integration. I don't know the command line.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;command.txt contains:&amp;nbsp;&lt;BR /&gt;C:\Program Files (x86)\Intel\oneAPI\vtune\2024.0\bin64&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Windows 11:&amp;nbsp;&lt;BR /&gt;OS Name: Microsoft Windows 11 Pro&lt;BR /&gt;OS Version: 10.0.22631 N/A Build 22631&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Log is attached.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 09:30:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596263#M24682</guid>
      <dc:creator>LukasT</dc:creator>
      <dc:date>2024-05-09T09:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596268#M24683</link>
      <description>&lt;P&gt;Is the issue observed only from MSVC? Did you reproduce the issue from VTune directly?&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 09:44:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596268#M24683</guid>
      <dc:creator>yuzhang3_intel</dc:creator>
      <dc:date>2024-05-09T09:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596285#M24684</link>
      <description>&lt;P&gt;Yes, also reproducible directly from the VTune GUI:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LukasT_0-1715250120426.png" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/54557iA3A076B30216B3B7/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="LukasT_0-1715250120426.png" alt="LukasT_0-1715250120426.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 10:23:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596285#M24684</guid>
      <dc:creator>LukasT</dc:creator>
      <dc:date>2024-05-09T10:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596286#M24685</link>
      <description>&lt;P&gt;Did you try to attach one simple process instead of the current process? Please attach the VTune data.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 10:26:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596286#M24685</guid>
      <dc:creator>yuzhang3_intel</dc:creator>
      <dc:date>2024-05-09T10:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596293#M24686</link>
      <description>&lt;P&gt;I'm able to profile&amp;nbsp;c:\Qt\5.15.2\msvc2019_64\bin\qdbusviewer.exe just fine for example:&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LukasT_0-1715253026677.png" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/54559iC15BCA325D9F4B07/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="LukasT_0-1715253026677.png" alt="LukasT_0-1715253026677.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The Intel VTune symbol resolution process crashes only for our proprietary project.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 11:11:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596293#M24686</guid>
      <dc:creator>LukasT</dc:creator>
      <dc:date>2024-05-09T11:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596308#M24687</link>
      <description>&lt;P&gt;Could you post the command line copied from the VTune GUI below? Please attach the VTune data if possible.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="yuzhang3_intel_0-1715258101948.png" style="width: 400px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/54560i8389008CD4DB6DB5/image-size/medium?v=v2&amp;amp;px=400&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="yuzhang3_intel_0-1715258101948.png" alt="yuzhang3_intel_0-1715258101948.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 12:51:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596308#M24687</guid>
      <dc:creator>yuzhang3_intel</dc:creator>
      <dc:date>2024-05-09T12:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: Intel VTune started to crash: gh2::error::FailedTo.Process.The.Paramet</title>
      <link>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596404#M24688</link>
      <description>&lt;P&gt;Hm...the bug is gone. I cannot reproduce it anymore.&lt;BR /&gt;&lt;BR /&gt;I recalled I added symbols for nvidia recently:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://driver-symbols.nvidia.com/" target="_blank"&gt;https://driver-symbols.nvidia.com/&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;but when I added it back it still does not crash.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Command-line:&amp;nbsp;&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Intel\oneAPI\vtune\2024.0\bin64\vtune" -collect hotspots --app-working-dir=V:\build\product\ -- V:\build\product\bin\RelWithDebInfo\Milo-Product.exe&lt;BR /&gt;&lt;BR /&gt;Not sure what happened, but the crash is not reproducible, I can profile again.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 17:07:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Intel-VTune-started-to-crash-gh2-error-FailedTo-Process-The/m-p/1596404#M24688</guid>
      <dc:creator>LukasT</dc:creator>
      <dc:date>2024-05-09T17:07:09Z</dc:date>
    </item>
  </channel>
</rss>

