# Extension Manager search is not functioning as expected

**URL:** <https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370>\
**Category:** Support\
**Tags:** extensions-manager\
**Created:** [May 24, 2017, 1:18pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370 "2017-05-24T13:18:40Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [May 24, 2017, 1:18pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/1 "2017-05-24T13:18:40Z")

</div>

Search results do not make sense to me.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/0/c0bd404e5844a373e6502087f5d1898a6d9f7ed6.png)

---

<div class="post-metadata">

**Author:** ![tdiprima](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/tdiprima/32/9469_2.png) [@tdiprima](https://discourse.slicer.org/u/tdiprima)\
**Post date:** [May 24, 2017, 2:07pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/2 "2017-05-24T14:07:32Z")

</div>

Agreed. When I go to install the SlicerPathology extension, and bring up the extension wizard, there are 3 slicer pathologies. And 3 ChangeTrackers.

Prior to re-install, I deleted the NA-MIC folder inside of AppData/Roaming. So there was no cached copy there to cause the triplicates.

The fix was – I had to reboot the machine TWICE. The second time I did a hard reboot. So maybe a full shutdown and restart was the answer.

So far we’ve seen this behavior on multiple Windows machines. (And @fedorov it looks like you’re using Mac, right?)

Thanks.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/3/1/310ac0feb24a52dc5f1c52930f698233be4fcc04.png)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 24, 2017, 2:28pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/3 "2017-05-24T14:28:34Z")

</div>

I’ve experienced random slowdowns non-responses, too (progress stuck at 10%, no extensions come up; after restarting Slicer and the extension manager everything worked).

Probably not related to Slicer, as [loading the extension manager directly from a browser](http://slicer.kitware.com/midas3/slicerappstore) has similar issues, too.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [May 24, 2017, 3:52pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/4 "2017-05-24T15:52:16Z")

</div>

> [@tdiprima](#):
>
> @fedorov it looks like you’re using Mac, right?

correct, I am using mac

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [May 25, 2017, 3:40pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/5 "2017-05-25T15:40:37Z")

</div>

I’m also seeing severe hangs in the extension manager and the online view.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 25, 2017, 4:04pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/6 "2017-05-25T16:04:38Z")

</div>

earlier today for me it hung for quite a while but finally succeeded.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [May 25, 2017, 4:57pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/7 "2017-05-25T16:57:59Z")

</div>

I think there could be 2 separate (or related?) issue:

1. Search succeeds, but search results are incorrect (this is what I initially reported).
2. Extension browser hangs or takes very long time to load.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 25, 2017, 5:14pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/8 "2017-05-25T17:14:51Z")

</div>

> [@fedorov](#):
>
> Search succeeds, but search results are incorrect (this is what I initially reported

First of all, the filtering was correct. ChangeTracker extension has “pathology” word in its description.  
Duplicate listings has been popping up randomly in the last few years (with or without any filtering applied). It’s not nice and it should be fixed, but otherwise harmless.

> [@fedorov](#):
>
> Extension browser hangs or takes very long time to load.

That’s a new issue and it’s severe. The wait is long enough so that people don’t wait for the result and conclude that Slicer is broken. It should be fixed ASAP. Probably the simplest solution would be to not spend time with determining the latest available version when a specific version is already supplied (or never try to determine latest version but just display a meaningful error message to let the user know what is missing and how to get that information).

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [May 25, 2017, 6:14pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/9 "2017-05-25T18:14:35Z")

</div>

> [@lassoan](#):
>
> First of all, the filtering was correct.

Can you explain the presence of CMFreg? Perhaps there is an explanation, but I don’t see any mentioning of “pathology” in the extension metadata. But I don’t know what other sources Extensions Manager is searching. It’s confusing.

> <https://github.com/Slicer/ExtensionsIndex/blob/master/CMFreg.s4ext>

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 25, 2017, 9:10pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/10 "2017-05-25T21:10:43Z")

</div>

Good point. Most likely CMFreg (and all other extensions than ChangeTracker and SlicerPathology) are duplicate items left over from the time when the filtering criteria was still just “pa”.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 26, 2017, 2:26pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/11 "2017-05-26T14:26:49Z")

</div>

@jcfr This extension manager hang is very confusing for users. If it’s too difficult to properly fix it then maybe just temporarily revert the latest developments and enable them again once the performance issue is sorted out.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 29, 2017, 9:55pm UTC](https://discourse.slicer.org/t/extension-manager-search-is-not-functioning-as-expected/370/12 "2017-05-29T21:55:54Z")

</div>

Behavior should now be back to normal when used within Slicer. Generally speaking, the slow lookup is performed only if needed.

> <https://github.com/midasplatform/slicerappstore/commit/71d41e938cb7021a7d7659834bd5c55112d39479>