i ran the above R report on our test server. i just took a look at it and saw an R process taking up ~10gb of virtual memory (attached). i closed the browser after it was clear the above R report wasnt going to load, but apparently those keep running. clearly trying to graph 700K rows is not good. i would argue that not respecting the QWP filters when switching to an R report is a bug.