# Help finding what's causing a semi-hang

**URL:** <https://discourse.julialang.org/t/help-finding-whats-causing-a-semi-hang/43805>\
**Category:** General Usage\
**Created:** [July 28, 2020, 9:03am UTC](https://discourse.julialang.org/t/help-finding-whats-causing-a-semi-hang/43805 "2020-07-28T09:03:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![akdor1154](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/akdor1154/32/15975_2.png) [@akdor1154](https://discourse.julialang.org/u/akdor1154)\
**Post date:** [July 28, 2020, 9:03am UTC](https://discourse.julialang.org/t/help-finding-whats-causing-a-semi-hang/43805/1 "2020-07-28T09:03:24Z")

</div>

Hey guys,  
I’ve just found some really strange (and irritating) behaviour: when both IndexedTables and DataFrames are `using`-ed, `IndexedTables.table()` takes like 5 minutes to run if a certain argument is passed. To reproduce:

```julia
using DataFrames
using IndexedTables
# this is fine
IndexedTables.table((a = ['a', 'b', 'c'], b=[1,2,3]))
# semi-hang here, can't use Ctrl+C to get a stacktrace, takes about 5 minutes on my machine
IndexedTables.table((a = ['a', 'b', 'c'], b=[1,2,3]), pkey=(:a,))

```

If DataFrames is not imported then it works fine.  
I am suspecting compiler fickleness but I don’t really know enough to look into it. Any pointers on debugging this? Tried with 1.4.0 and 1.5.0-rc2.