When I attempt to open a file, all I get is a pink background with red dots
Any idea what may be causing this?
When I attempt to open a file, all I get is a pink background with red dots
Any idea what may be causing this?
Hi @shillate! Welcome!
Three things that might be helpful here:
</>
button at the top of the posting box to format what you paste (keeps the forum software from garbling it!). If the output is too long to paste in here, please share it online somewhere else and post a link.Also, is this sort of like what you're seeing? (Click the down arrow to expand the preview so you can see the screenshot)
(Unfortunately, I don't think there was ever a resolution to the problem described in that topic)
Here is the report:
[1] "1.1.463"
$R
[1] "C:\PROGRA~1\R\R-35~1.1\bin\x64\R.exe"
$pdflatex
[1] "C:\texlive\2017\bin\win32\pdflatex.exe"
$bibtex
[1] "C:\texlive\2017\bin\win32\bibtex.exe"
$gcc
[1] ""
$git
[1] ""
$svn
[1] ""
R version 3.5.1 (2018-07-02)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows >= 8 x64 (build 9200)
Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252 LC_CTYPE=English_United States.1252 LC_MONETARY=English_United States.1252 LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] compiler_3.5.1 tools_3.5.1 yaml_2.2.0
SysInfo:
sysname release version nodename machine login user effective_user
"Windows" ">= 8 x64" "build 9200" "DESKTOP-QJILMRV" "x86-64" "shill" "shill" "shill"
R Version:
Thanks! How odd.
Does this happen with all types of files (.R, .Rmd, .txt), or only certain types of files — or only certain individual files? Can you post a file that displays this behavior somewhere (e.g. Google Drive, Pastebin, etc) and link to it?
This happens only with this one .Rmd file, but the other files can be painfully slow. I did a Microsoft memory scan/optimization and this seemed to do nothing. This all seemed to begin when I upgraded to the newest Rstudio version.
When I run the GPU diagnostics, it says the following:
GPU process was unable to boot: GPU access is disabled through commandline switch --disable-gpu.
Disabled Features: all
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Checker-imaging has been disabled via finch trial or the command line.
Disabled Features: checker_imaging
Data exported
2018-11-09T18:38:14.900Z
Chrome version
rstudio/1.2.1091.0
Operating system
Windows NT 10.0.17134
Software rendering list URL
https://chromium.googlesource.com/chromium/src/+/926d27280b919a1aeb0091392d56f63a38d2bc0b/gpu/config/software_rendering_list.json
Driver bug list URL
https://chromium.googlesource.com/chromium/src/+/926d27280b919a1aeb0091392d56f63a38d2bc0b/gpu/config/gpu_driver_bug_list.json
ANGLE commit id
unknown hash
2D graphics backend
Skia/65 35ee3617fcb08e0d79e6b9e6c05db23cc9416d4f-
Command Line
"C:\Program Files\RStudio\bin\rstudio.exe" --enable-viewport --disable-renderer-accessibility --browser-subprocess-path="C:\Program Files\RStudio\bin\QtWebEngineProcess.exe" --no-sandbox --enable-threaded-compositing --disable-zero-copy --disable-gpu-memory-buffer-compositor-resources --disable-gpu-memory-buffer-video-frames --disable-mojo-local-storage --disable-es3-gl-context --enable-features=AllowContentInitiatedDataUrlNavigations --disable-features=SurfaceSynchronization --disable-features=SurfaceSynchronization,TouchpadAndWheelScrollLatching --disable-gpu
Initialization time
0
In-process GPU
true
Passthrough Command Decoder
false
Direct Composition
false
Supports overlays
false
Sandboxed
false
GPU0
VENDOR = 0x8086, DEVICE= 0x1916
GPU1
VENDOR = 0x10de, DEVICE= 0x1427
Optimus
false
Optimus
false
AMD switchable
false
Desktop compositing
Aero Glass
Diagonal Monitor Size of \.\DISPLAY1
13.4"
Driver vendor
Intel Corporation
Driver version
24.20.100.6136
Driver date
5-25-2018
Pixel shader version
Vertex shader version
Max. MSAA samples
Machine model name
Machine model version
GL_VENDOR
GL_RENDERER
GL_VERSION
GL_EXTENSIONS
Disabled Extensions
Disabled WebGL Extensions
Window system binding vendor
Window system binding version
Window system binding extensions
Direct rendering
Yes
Reset notification strategy
0x0000
GPU process crash count
0
Tile Update Mode
One-copy
Partial Raster
Enabled
ATC
Software only
ATCIA
Software only
DXT1
Software only
DXT5
Software only
ETC1
Software only
R_8
Software only
R_16
Software only
RG_88
Software only
BGR_565
Software only
RGBA_4444
Software only
RGBX_8888
GPU_READ, SCANOUT
RGBA_8888
GPU_READ, SCANOUT
BGRX_8888
Software only
BGRX_1010102
Software only
BGRA_8888
Software only
RGBA_F16
Software only
YVU_420
Software only
YUV_420_BIPLANAR
Software only
UYVY_422
Software only
Info
Display[2528732444] bounds=0,0 1500x1000, workarea=0,0 1500x960, scale=2, external
Color space information
{primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL}
Bits per color component
8
Bits per pixel
24
Those pink dots are used as replacement characters for data in the document that couldn't be decoded -- in other words, it's typically a sign that the document has become corrupted and replaced with garbage data.
If it only occurs for one file, then it would seem that one file somehow became corrupted -- your best bet would be to restore from backup.
So had to stop a random forest model (ranger
using caret
) that had been running for 17 hours on parallel (expected time duration was 2-3 hours based on similar models) and when the CPU usage didn't go down after having stopped the process, I decided to close RStudio and shut down my computer. Now when I open the R project in question, every rmarkdown
file within the project opens up looking like this. All the R scripts seem ok.
Am I to understand that each and every .Rmd file within the project is corrupt and beyond salvage? [sobs uncontrollably on the inside]
Any and all help appreciated.
Hlynur