Removing the vueComponent optional parameter from rollbar.error method helped me to prevent app freeze.

We had this exact issue in our app.
piyushsinghania's fix solved all issues for us when the underlying problem was an error being reported by Vue, however if there were warnings (such as computed property X is readOnly but was assigned to...) then the infinity-loop would still trigger. Adding a warningHandler solved this for us.

    app.config.errorHandler = (error, vm, info) => {
      rollbar.error(error, { info });
      console.error(error);
    };
    app.config.warnHandler = (msg, instance ,trace) => {
      console.warn(msg);
    };

I was also experiencing a similar freeze, rollbar.umn.min.js was hanging at this line:
try{for(o in e)(n=e[o])&&(i(n,"object")||i(n,"array"))?r.includes(n)?u[o]="Removed circular reference: "+s(n):((a=r.slice()).push(n)

@piyushsinghania 's fix has addressed it.

What rollbar functionality am I losing by removing the vueComponent parameter?

What rollbar functionality am I losing by removing the vueComponent parameter?

I have the same question as that of @amokrunnr

What rollbar functionality am I losing by removing the vueComponent parameter?

It can be safely omitted.

This is the object representing the component where the error happened. Not selective error info, but rather the full object.

This shows up as a custom key in the Rollbar error, when passed as shown in the example.

If you're seeing an issue like described above, or an issue related to the size of the object, it can be omitted, or you can pass only the part(s) you're interested in.