Neos 9: Insert Content References CPU 1100%

Using Neos & Flow
1

Hallo, during development stage I discovered, that after inserting several ‘Insert Content References‘ Nodetypes on my website, the CPU went wild to 1100%.

The so called process rg (ripgrep) caused the issue. Something is repeatedly triggering filesystem scans. I am manualy kill that process.

Does anyone also had this problem? or it’s something in my code which I took from demo package.

prototype(Custom.Site:ContentReferences.InsertContentReferences) < prototype(Neos.Neos:ContentComponent) {


  @context.referenceNodesArray = ${q(node).property('internalLink')}


  // ensure when node changes, references must be updated

  @cache {

    mode = 'cached'

    entryIdentifier {

      node = ${Neos.Caching.entryIdentifierForNode(node)}

    }

    entryTags {

      1 = ${Neos.Caching.nodeTag(node)}

      2 = ${Neos.Caching.nodeTag(referenceNodesArray)}

      3 = ${Neos.Caching.descendantOfTag(referenceNodesArray)}

    }

  }


  referenceNodes = Neos.Fusion:Loop {

    items = ${referenceNodesArray}

    itemRenderer = Neos.Neos:ContentCase

    itemName = 'node'




    // Disable ContentElementWrapping for references itself

    prototype(Neos.Neos:ContentElementWrapping) {

      @if.render = false

    }

    // Disable InlineEditable for references itself

    prototype(Neos.Neos:Editable) {

      renderer.editable.condition = false

    }

  }


  renderer = afx`

    <Neos.Fusion:Fragment @if.referencesSelected={props.referenceNodes}>{props.referenceNodes}</Neos.Fusion:Fragment>

  `

}
2

I supose it’s VS Code problem

3

Yes doesn’t sound like it’s coming from Neos.

But if you use the FileSystem based Caches and have a lot of entries, the IDE might be triggered by this.

So it’s best is to ignore Data/Temporary or the whole Data folder.

1 Like