Hi @wurz,
Unfortunately, we don’t have much to go off here. I see you already followed the suggestions from this related forum post.
I’m wondering whether memory may still be the bottleneck, e.g. it looks like R may bring its own configuration to limit available memory. If possible, successfully running the R script on a smaller or simpler set of data may provide further indication of resource bottlenecks.
The full logs that admins can download in the WebPortal may also provide a stack trace with additional details (assuming they are downloaded recently after the error occurred). Should this be the case, you’d be welcome to share them with our enterprise support (support@knime.com) for a further investigation.
Kind regards
Marvin