# Junction nodes think they are bigger than they are

**URL:** <https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474>\
**Category:** General\
**Created:** [31 January 2023 10:27 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474 "2023-01-31T10:27:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 January 2023 10:27 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/1 "2023-01-31T10:27:36Z")

</div>

I find that some of my junction nodes think they are bigger than they should be, so if they are not widely separated from adjacent nodes then they show the ! warning of overlapping nodes.

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/a/cacbe182dfea932c31cae4395214454213229013.png)

If I move the function node (or the junction) across a bit then it is ok. Is this a known issue?

```auto
[{"id":"b84ed6884f928965","type":"debug","z":"393002550c0f0617","name":"OP2","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":790,"y":580,"wires":[]},{"id":"50a4c0dfb602dde1","type":"junction","z":"393002550c0f0617","x":660,"y":580,"wires":[["b84ed6884f928965"]]}]

node-red 3.0.2
nodejs 18.13.0

```

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [31 January 2023 11:48 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/2 "2023-01-31T11:48:41Z")

</div>

> [@Colin](#):
>
> Is this a known issue?

First I have seen or heard.

It should probably be raised as an issue (not sure if that would be on the node-red or nr-lint repo though)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [31 January 2023 11:55 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/3 "2023-01-31T11:55:01Z")

</div>

My gut feel is nrlint - because it is making an assumption as to how 'big' the junction is in absence of concrete information.

That said, I'm sure I fixed that around the time we released Junctions originally...

Yup - [Handle junctions in overlapping-nodes rule by knolleary · Pull Request #33 · node-red/nrlint · GitHub](https://github.com/node-red/nrlint/pull/33) - and released in nrlint 1.1.0

What version are you using?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 January 2023 15:00 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/4 "2023-01-31T15:00:37Z")

</div>

> [@knolleary](#):
>
> Yup - [Handle junctions in overlapping-nodes rule by knolleary · Pull Request #33 · node-red/nrlint · GitHub](https://github.com/node-red/nrlint/pull/33) - and released in nrlint 1.1.0

That was it, upgrading sorting it. Thanks.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 January 2023 15:10 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/5 "2023-01-31T15:10:18Z")

</div>

Unfortunately, having upgraded to 1.1.0 (from 1.0.2) Chrome (or Firefox) is now permanently hogging the processor when I open localhost:1880.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 February 2023 16:11 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/6 "2023-02-01T16:11:51Z")

</div>

Any suggestions on how I work out which function is causing the processor hogging? When I roll back nlrint it is ok.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [1 February 2023 16:38 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/7 "2023-02-01T16:38:27Z")

</div>

You had hit this before (which is why you had stuck on the older version) - [Node red tab hogging the processor in the browser · Issue #36 · node-red/nrlint · GitHub](https://github.com/node-red/nrlint/issues/36)

You provided me your flows at the time and I used them to track down exactly which node it was - [Node red tab hogging the processor in the browser · Issue #36 · node-red/nrlint · GitHub](https://github.com/node-red/nrlint/issues/36#issuecomment-1198553887)

I raised the upstream issue, but it appears 'upstream' has been abandoned and no fix is forth coming. We need to figure out a way around the issue... which is less than ideal.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 February 2023 17:11 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/8 "2023-02-01T17:11:52Z")

</div>

Sorry Nick. I am getting too old. I did remember that there had been a problem but I didn't remember that I had rolled back as a workaround. I have removed that code and it is ok now.

> [@knolleary](#):
>
> it appears 'upstream' has been abandoned

That is a pain.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [2 April 2023 17:12 UTC](https://discourse.nodered.org/t/junction-nodes-think-they-are-bigger-than-they-are/74474/9 "2023-04-02T17:12:46Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.