Nebula crashes when running query with `WHERE 1 IS NULL` (control `WHERE false` works)

[zihaozeng0021]

Configuration

Nebula Version: 2025.10.28-nightly

Operating System: WSL2 – Ubuntu 24.04.1 LTS

Installation Method: Docker

---

Steps to reproduce

1. Start Nebula via Docker

docker exec -it nebula-docker-compose-console-1 sh

2. Connect with nebula-console:

nebula-console -u root -p nebula -addr graphd -port 9669

3. Run the following query:

Create a test space

CREATE SPACE IF NOT EXISTS test(partition_num=1, replica_factor=1, vid_type=FIXED_STRING(8));

Select the space

use test

The buggy query:

(root@nebula) [test]> UNWIND range(1,10000) AS p WITH p LIMIT 1000 UNWIND range(1,2000000) AS qid WITH p, qid, {age: qid % 50 + 18, score: qid % 100} AS q WHERE 1 IS NULL RETURN p
2025/12/25 14:47:24 Loop error, failed to reconnect, failed to open transport, error: dial tcp 172.19.0.10:9669: connect: connection refused

A control Query:

(root@nebula) [test]> UNWIND range(1,10000) AS p WITH p LIMIT 1000 UNWIND range(1,2000000) AS qid WITH p, qid, {age: qid % 50 + 18, score: qid % 100} AS q WHERE false RETURN p
+---+
| p |
+---+
+---+
Empty set (time spent 5.615ms/6.29917ms)

---

Expected behaviour

Both queries should return an empty result set, because both predicates are constant-false (1 IS NULL and false).

Actual behaviour

The buggy query causes the client to lose the connection; The control query succeeds and returns an empty set.

[kuaikuai]

Nebula Graph’s graphd is experiencing OOM ssues.