[Rcpp-devel] `checkUserInterrupt()` might not be safe if Rcout is used.

Wush Wu wush978 at gmail.com
Thu Jul 26 17:18:11 CEST 2018

Hi all,

I just learned the function `checkUserInterrupt` and played with it in my
package today. At first, everything was good. However, I sensed something
wrong when I interrupted my function and relaunched it. In my case, the
thread number of OpenMP decreased to 1 after an user interruption.

According to the documentation, the `checkUserInterrupt` will throw an
exception to trigger the C++ destructors on the stack. However, if I use
`Rcout` several times (verbose mode of my function), then it will not throw
the exception but leave the function directly.

Here is a toy example to demonstrate:

It uses `Rcout` / `std::cout` as a progressbar and check the user
interruption. If the exception is thrown correctly, then a catch clause
will handle the exception and write something to the `std::cerr`.

If I turn off the verbose mode, then the `checkUserInterrupt` always throws
the exception.

If I turn on the verbose mode and use `jsize` to select the number of dot
on the screen, then the `checkUserInterrupt` will exit the function
immediately if `jsize` is large.  For example, `checkUserInterrupt` throws
exception if `jsize = 5` but does not throw if `jsize = 100`.

If I use `std::cout` instead of `Rcpp::Rcout`, then everything goes right
again. So, there might be something wrong even if `R_TopLevelExec` is used.

Well, I guess this bug might be hard to debug, but we should let the others
aware about this at least, right?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20180726/01b0536e/attachment.html>

More information about the Rcpp-devel mailing list