<?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 deadlock when using advisor+openblas+threading in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141690#M17084</link>
    <description>&lt;P&gt;Hope this is the right place to report the following issue.&lt;/P&gt;

&lt;P&gt;Context: I'm using Advisor with a Python/C code (Python calls C functions to speed up expensive code sections).&lt;BR /&gt;
	&lt;BR /&gt;
	Issue: I get non-deterministic deadlocks (the program stops executing) unless I disable threading. No problems w/o Advisor.&lt;/P&gt;

&lt;P&gt;More insights: Initially, I (empirically) observed that no deadlock happening when setting OMP_NUM_THREADS=1. Then, I observed (again empirically) no deadlock w/o importing NumPy. My NumPy uses OpenBLAS underneath. So I tried disabling both OpenBLAS threading (OPENBLAS_NUM_THREADS=1) and Numaexpr threading (NUMEXPR_NUM_THREADS=1), leaving OMP_NUM_THREADS unset. Result: no deadlock (hence the thread title).&lt;/P&gt;

&lt;P&gt;Unfortunately, I couldn't come up with a minimal reproducible example (or better, I do have one which is only five lines, but it requires importing my own Python modules). Before trying harder, I wonder whether there's an explanation off top of your head, or whether I'm doing something stupid (entirely possible)?&lt;/P&gt;

&lt;P&gt;my command line is no special:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
	&lt;P&gt;advixe-cl -data-limit=500&amp;nbsp; -collect survey&amp;nbsp; -project-dir myprojdir -search-dir src:r=/tmp -run-pass-thru=--no-altstack -- python myprogram.py&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;-- Fabio&lt;/P&gt;</description>
    <pubDate>Sun, 17 Jun 2018 11:45:53 GMT</pubDate>
    <dc:creator>FabioL_</dc:creator>
    <dc:date>2018-06-17T11:45:53Z</dc:date>
    <item>
      <title>deadlock when using advisor+openblas+threading</title>
      <link>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141690#M17084</link>
      <description>&lt;P&gt;Hope this is the right place to report the following issue.&lt;/P&gt;

&lt;P&gt;Context: I'm using Advisor with a Python/C code (Python calls C functions to speed up expensive code sections).&lt;BR /&gt;
	&lt;BR /&gt;
	Issue: I get non-deterministic deadlocks (the program stops executing) unless I disable threading. No problems w/o Advisor.&lt;/P&gt;

&lt;P&gt;More insights: Initially, I (empirically) observed that no deadlock happening when setting OMP_NUM_THREADS=1. Then, I observed (again empirically) no deadlock w/o importing NumPy. My NumPy uses OpenBLAS underneath. So I tried disabling both OpenBLAS threading (OPENBLAS_NUM_THREADS=1) and Numaexpr threading (NUMEXPR_NUM_THREADS=1), leaving OMP_NUM_THREADS unset. Result: no deadlock (hence the thread title).&lt;/P&gt;

&lt;P&gt;Unfortunately, I couldn't come up with a minimal reproducible example (or better, I do have one which is only five lines, but it requires importing my own Python modules). Before trying harder, I wonder whether there's an explanation off top of your head, or whether I'm doing something stupid (entirely possible)?&lt;/P&gt;

&lt;P&gt;my command line is no special:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
	&lt;P&gt;advixe-cl -data-limit=500&amp;nbsp; -collect survey&amp;nbsp; -project-dir myprojdir -search-dir src:r=/tmp -run-pass-thru=--no-altstack -- python myprogram.py&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;-- Fabio&lt;/P&gt;</description>
      <pubDate>Sun, 17 Jun 2018 11:45:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141690#M17084</guid>
      <dc:creator>FabioL_</dc:creator>
      <dc:date>2018-06-17T11:45:53Z</dc:date>
    </item>
    <item>
      <title>Forgot one important detail.</title>
      <link>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141691#M17085</link>
      <description>&lt;P&gt;Forgot one important detail. The issue above is from the latest stable release&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
	&lt;P&gt;amplxe-cl --version&lt;BR /&gt;
		Intel(R) VTune(TM) Amplifier 2018 Update 3 (build 558279) Command Line Tool&lt;BR /&gt;
		Copyright (C) 2009-2018 Intel Corporation. All rights reserved.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Mon, 18 Jun 2018 07:29:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141691#M17085</guid>
      <dc:creator>FabioL_</dc:creator>
      <dc:date>2018-06-18T07:29:10Z</dc:date>
    </item>
    <item>
      <title>Ideally Advisor should work</title>
      <link>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141692#M17086</link>
      <description>&lt;P&gt;Ideally&amp;nbsp;Advisor should work with multiple threads in underlying libraries, so most probably it is a bug.&lt;/P&gt;

&lt;P&gt;Could you try to run survey collection by attaching to running python process and see if this helps?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jun 2018 14:31:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/deadlock-when-using-advisor-openblas-threading/m-p/1141692#M17086</guid>
      <dc:creator>Egor_K_Intel</dc:creator>
      <dc:date>2018-06-22T14:31:42Z</dc:date>
    </item>
  </channel>
</rss>

