similar to: R 4.0.2 64-bit Windows hangs

Thanks for the response. Having spent a lot of the day trying to solve this, as R is essential for my workflow, I've tried to debug via the binary only as I haven't yet got the toolchain working - I'm quite inexperienced at this. I've confirmed the problem is exactly as described in the initial (albeit old) bug report. The exception that's thrown within Visual Studio is:

I am having exactly the same issue as the following bug report: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16515. RTerm.exe hangs on startup, nothing is printed to the terminal. 32-bit RTerm.exe runs fine. No errors are displayed, but I see the same as the bug report in Event Viewer. I am running Windows 10 64-bit, v2010. ---- Sent using Guerrillamail.com Block or report abuse:

Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. I will continue to look into the issue with the methods Tomas mentioned. Many thanks. On 2020-08-21 21:05:51 nospam at altfeld-im.de wrote: > May be unrelated but on SO there is a report that a

I'm only using Visual Studio to debug. I'm using R version 4.0.2 from: https://cran.r-project.org/, and have tested the patched version. Even the x64 version of the previous version of R (3.6) does not run. I have previously had Microsoft R Open installed on the machine, but it's been uninstalled. Thanks. On 2020-08-21 18:48:42 murdoch.duncan at gmail.com wrote: > Are you

On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: > Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. > > I will continue to look into the issue with the methods Tomas mentioned. It is interesting that a rare 5 years old problem

https://bugs.freedesktop.org/show_bug.cgi?id=110500 Bug ID: 110500 Summary: X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium

It'd be nice of the page at https://www.centos.org/docs/ at least provided a link to the Red Hat 6 documentation at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/index.html. Something along the lines of: For version 6 documentation please refer to: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/index.html ---- Sent using

On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: > > Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. > > > > I will

On 8/22/20 8:26 PM, Tomas Kalibera wrote: > On 8/22/20 7:58 PM, Jeroen Ooms wrote: >> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera >> <tomas.kalibera at gmail.com> wrote: >>> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >>>> Ah yes, this is related. I reported v2010 below, but it looks like >>>> I was updated to this

Dear all, Two questions regarding rterm First: C:\Program Files\R\rw1081\bin\rterm.exe --vanilla <test.r --args "Arg1" "Arg2" worked for me so far with r Version 1081, to start a R script with the given arguments. With R1090 C:\Program Files\R\rw1090\bin\rterm.exe --vanilla <test.r --args "Arg1" "Arg2" There is the error message: Rterm.exe

Full_Name: Russell V. Lenth Version: 2.3.1 OS: Windows XP Pro Submission from: (NULL) (128.255.132.188) I wrote a simple .BAT file to run the Sweave function on a file (via RTerm), then run pdflatex on the result (after RTerm exits). The issue is that if an error condition occurs in RTerm, it is prudent to not do the pdflatex processing afterward. Here are the relevant statements in the BAT

Hello Users: I'm using R version 2.0.1, and having problems with RODBC. Everything works fine when I use Rgui, but when I try to use Rterm and issue the commands library(RODBC) con <- odbcConnect("MySQL", "test") I get the following error: Error in sqlQuery(con, str) : first argument is not an open RODBC channel In addition: Warning messages:

On 8/22/20 7:58 PM, Jeroen Ooms wrote: > On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >>> Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R

Please, help with announcing an error from Rterm: I am calling R from an Excel VBA and noticed that if there is an error nothing conspicuous happens. I would like just a popup window when R cannot finish cleanly. The "ret " value returned from Shell is useless in determining what happened. Thank you all. ***************************** Public Sub Repo() ds = InputBox("Type in

Colleagues, I have encountered the following situation in R (2.9.0) with Windows XP. I have an application that calls Rterm.exe. In certain situations, the application terminates but fails to close R. Then, the next time that the application runs, there are replicated copies of R running - this slows the system. One solution would be to kill any open versions of Rterm.exe each time

On 8/22/20 9:33 PM, Jeroen Ooms wrote: > On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 8/22/20 8:26 PM, Tomas Kalibera wrote: >>> On 8/22/20 7:58 PM, Jeroen Ooms wrote: >>>> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera >>>> <tomas.kalibera at gmail.com> wrote: >>>>> On 8/21/20 11:45

I've been trying to use Rterm.exe, mainly because of Rgui.exe's lack of support for incremental history searching. But on my system (Win XP, SP3), it (rterm from R-2.8.1) frequently just stops responding to keyboard input. This happens often (enough to make it unusable), and generally after a switch to another window. It doesn't seem to hang exactly, as if I leave it a while (minutes)

Hi, I'm running R v1.9.0 on WinXP Pro. I noticed that R.exe and Rterm.exe behave differently on Ctrl-C. Starting a Windows Command prompt (cmd.exe) you get from running Rterm.exe: C:\Program Files\R>rw1090\bin\Rterm.exe --vanilla --quiet > ^C > ^C > 1+1 [1] 2 > Sys.sleep(100) # Ctrl-C after a few seconds > ^C > ^C > 1+1 [1] 2 > q() C:\Program Files\R>

On Sat, Aug 22, 2020 at 9:10 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/22/20 8:26 PM, Tomas Kalibera wrote: > > On 8/22/20 7:58 PM, Jeroen Ooms wrote: > >> On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera > >> <tomas.kalibera at gmail.com> wrote: > >>> On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: >

Dear R users, Does anyone notice that Rterm.exe does not work well with rxvt.exe, an xterm emulator for Cygwin? It produces an error message window with the following message: This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor It also prints "Signal 127" in rxvt window. Rterm --ess, however, works.