Some path queries do not render graph results, subsequent :schema or :queries produce nothing

[luanne]

Some types of path queries such as

MATCH network = (:Person {name:"JARED KUSHNER"})-[*..2]-()
RETURN network

does not render graph or table results in the Neo4j Browser; only code view works.
After this, :schema or :queries start saying "No Indexes No Constraints" even though they exist, and no queries listed. Hard page reset seems to fix this.
The JS console reports

Explorer.jsx:81 Uncaught (in promise) TypeError: Cannot read property 'filter' of undefined
    at eval (Explorer.jsx:81)
    at Array.filter (<anonymous>)
    at new ExplorerComponent (Explorer.jsx:78)
    at createComponent (preact.esm.js:586)
    at buildComponentFromVNode (preact.esm.js:816)
    at idiff (preact.esm.js:363)
    at innerDiffNode (preact.esm.js:482)
    at idiff (preact.esm.js:405)
    at diff (preact.esm.js:314)
    at renderComponent (

at about the time the path query finishes.

Neo4j Version: 3.2.5
Operating System: macOS Sierra 10.12.6
Component Neo4j Browser

Steps to reproduce

1. Import the Trumpworld dataset
2. Create constraints
3. Verify they exist with :schema
4. Verify that :queries lists queries
5. Run

MATCH network = (:Person {name:"JARED KUSHNER"})-[*..2]-()
RETURN network

Expected behavior

1. Graph results
2. :schema lists constraints correctly
3. :queries lists queries

Actual behavior

1. No graph or table results
2. :schema says No constraints
3. :queries lists nothing

[oskarhane]

Thanks for the report @luanne!
This is quite odd. It looks like Neo4j 3.2.2 have the same issue.
If you LIMIT the query to 300 or less, it seems to work. Can you confirm that?

The reason :schema and other things stop working is because the error breaks the app.
I'll make sure we catch it, and also fix the actual bug.

[luanne]

@oskarhane yes, confirming that <300 limit works correctly