The version reported by X11 in 10.5.5 is 2.1.5 to distinguish it from the 2.2.x series which contains a much newer userland. Most of the userland, however, only saw security updates. 10.5.5ġ0.5.5 contains updates to the X11 server to match what shipped with 2.2.3 ( xorg-server-1.3.0-apple22). The 2008-002 Security Update version of X11 is the same as 10.5.2 with some security fixes applied. The launchd mechanism to start X11 in 10.5.2 is unique to Apple’s 10.5.2 and never appeared in a release from this site in that form (though it was essentially integrated into xinit for 2.1.2). XQuartz 2.5.0 - First release supported on Snow Leopardġ0.5.2’s version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site. XQuartz 2.7.0 - First release supported on Lion XQuartz 2.7.2 - First release supported on Mountain Lion XQuartz 2.7.5 - First release supported on Mavericks XQuartz 2.7.7 - First release supported on Yosemite XQuartz 2.7.8 - First release supported on El Capitan XQuartz 2.7.11 - Last release to support Snow Leopard, Lion, and Mountain Lion XQuartz 2.8.0_alpha1 - Pre-Release, First pre-release with native Apple Silicon support Next message: rgl crashes after one successful draw on R.XQuartz 2.8.0 - First release with native Apple Silicon support.> stats graphics grDevices utils datasets methods base > Perhaps something is corrupt with my X11 window system? Thanks, Bryan And the same thing happens if I just do the commands inside the function individually. If I don't close the open rgl windows, it doesn't crash, and I can execute the function over and over successfully. > This will probably work fine for any of you, it's so simple and fundamental. > showSomething() # crashes R with the following report: > reproduce it while running in gdb or some other debugger? > able to reproduce this, it looks really hard to track down. > order and leaves rgl in an unstable state. > guessing the destruction of the old window triggers events in the wrong > I don't see it, but it looks to me like it may be a timing problem. > After narrowing things down, here's how to reproduce: > This is really odd, and probably 100% local to me, but I'm at a loss as to a next step. > NOTE: problem is with R.app, looks OK on command line R > On May 29, 2013, at 4:37 PM, Duncan Murdoch wrote: > 612 ::Window xparent = RootWindow(xdisplay, DefaultScreen(xdisplay)) > Program received signal EXC_BAD_ACCESS, Could not access memory. > I doubt that this is helpful, but I get: > goedman at > On May 29, 2013, at 2:49 PM, Roger Koenker wrote: > Do you ever see an rgl window pop-up? Just wondering if this is the same issue. > On May 29, 2013, at 5:17 PM, Robert J Goedman wrote: > goedman at > On May 29, 2013, at 3:19 PM, Roger Koenker wrote: > Not sure if that would fix it, but my system is the patched R.3.0.1, using XQuartz 2.7.4 and a slightly newer version of rgl (rgl_0.93.940). > On May 29, 2013, at 5:41 PM, Robert J Goedman wrote: > email rkoenker at Department of Economics > and also close the windows that are created. I upgraded to XQuartz 2.7.4 and now can run example(rgl) > goedman at > On May 29, 2013, at 3:57 PM, Roger Koenker wrote: > Repeatedly just 'example(plot3d)' and each time removing all rgl windows, will lead to the same problem Bryan mentioned this morning. > Great, like with Rcmdr, example(rgl) seems to work well. On May 29, 2013, at 7:16 PM, Robert J Goedman wrote: Unfortunately, I already have XQuartz 2.7.4 and it gives the problem I reported. Next message: rgl crashes after one successful draw on R.app.Previous message: rgl crashes after one successful draw on R.app.rgl crashes after one successful draw on R.app Bryan Hanson hanson at Rgl crashes after one successful draw on R.app
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |