Re: [Rpy] Error during wrapup: C stack usage is too close to the limit

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I can reproduce it with python-2.5 / R-2.6.1 as well.

The error might well only have to do with X11 devices only, so
I wanted to try R-2.7.0 (since it will/should be using cairo devices
by default), but no luck: I already get error a RunTime error at load
time :-/ .

On the other end, I managed to try the code in the example with a
rewrite of rpy I am working on and R-2.7-alpha: no more crashing on
the C stack, but no refresh on resize (so blank window after
resizing).

Are Microsoft Windows users observing the C stack problem ?

L.

2008/4/9, A_Berger <ag...@co...>:
>
>  I've been experiencing this error with several versions of rpy. The only
>  version that did work properly was Rpy1RC3, however newer versions of R
>  require newer versions of Rpy, and I had to update to a newer Rpy and
>  survive with the error. I've heard that this issue only arises on *nix
>  systems (i.e linux).
>  There are two errors that occur indistinctly when redrawing the X
>  display containing a plot.
>  Here is how it can be reproduced
>
>  --------------------------------------------------------------------------------------------------------
>  ~$ R
>
>  R version 2.5.1 (2007-06-27)
>  Copyright (C) 2007 The R Foundation for Statistical Computing
>  ISBN 3-900051-07-0
>
>  R is free software and comes with ABSOLUTELY NO WARRANTY.
>  You are welcome to redistribute it under certain conditions.
>  Type 'license()' or 'licence()' for distribution details.
>
>   Natural language support but running in an English locale
>
>  R is a collaborative project with many contributors.
>  Type 'contributors()' for more information and
>  'citation()' on how to cite R or R packages in publications.
>
>  Type 'demo()' for some demos, 'help()' for on-line help, or
>  'help.start()' for an HTML browser interface to help.
>  Type 'q()' to quit R.
>   > plot(c(1,2,3),c(4,5,6))
>   > >>>>>>>>>>>>>>    This plots a figure in X that can be resized,
>  minimized and closed without errors
>   >
>  Save workspace image? [y/n/c]:
>  Save workspace image? [y/n/c]: y
>  ~$ python
>  Python 2.5.1 (r251:54863, Mar  7 2008, 04:10:12)
>  [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
>  Type "help", "copyright", "credits" or "license" for more information.
>   >>> import rpy
>   >>> rpy.r.plot([1,2,3],[4,5,6])
>   >>>>>>>>>>>>>>>this plots a figure in X, when resizing, minimising, and
>  whenever the  X has to be redrawn, it kicks this error and terminates
>  the python session with error
>
>  >>> Error during wrapup: C stack usage is too close to the limit
>
> *** stack smashing detected ***: python terminated
>  Aborted (core dumped)
>  ~$
>  ------------------------------------------------------------------------------------------------------------
>  sometimes this error is produced, and the X display stays open and
>  zombie, but control is returned to python
>
>   >>> rpy.r.plot([1,2,3],[4,5,6])
>
>  >>> Error during wrapup: C stack usage is too close to the limit
>
>   *** caught segfault ***
>
> address 0x18, cause 'memory not mapped'
>
>
>  Possible actions:
>  1: abort (with core dump, if enabled)
>  2: normal R exit
>  3: exit R without saving workspace
>  4: exit R saving workspace
>  Selection:
>   >>>
>
> ---------------------------------------------------------------------------------------------------------
>
>  Hope this can be solved. I'm willing to collaborate, but have no idea
>  where to start. Any clues?
>  Thanks
>
>  Andres
>
>
>
>
>  Lukasz Szybalski wrote:
>  > On Wed, Apr 9, 2008 at 3:26 AM, Laurent Gautier <lga...@gm...> wrote:
>  >
>  >> Issues with the C stack are encountered now and then, and this might
>  >>  be a problem
>  >>  with R:
>  >>  http://tolstoy.newcastle.edu.au/R/e4/help/08/01/2069.html
>  >>
>  >>  More generally, whenever the host application (here the Python
>  >>  process) is manipulating the stack (like when using threads I think)
>  >>  the problem might be more likely to appear.
>  >>
>  >>  What is probably needed is a 100% reproducible example (I have not
>  >>  looked at Lucas' yet) that would help locate precisely (and hopefully
>  >>  fix) the problem.
>  >>
>  >>
>  >
>  > So who ever experienced a similar error, could you try:
>  >
>  > I get an error here on each machine I have:
>  >
>  >
>  >>>> from rpy import *
>  >>>> x = range(1,11)
>  >>>> y = [i**2 for i in x]
>  >>>> z = [i**3 for i in x]
>  >>>> r.plot(x, y, main='My second plot', xlab='x', ylab='y', type='l',
>  >>>>
>  > col='blue')
>  >
>  >>>> r.lines(x, z, col='red')
>  >>>>
>  >
>  >
>  > Lucas
>  >
>  > -------------------------------------------------------------------------
>  > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  > Don't miss this year's exciting event. There's still time to save $100.
>  > Use priority code J8TL2D2.
>  > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  > _______________________________________________
>  > rpy-list mailing list
>  > rpy...@li...
>  > https://lists.sourceforge.net/lists/listinfo/rpy-list
>  >
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  rpy-list mailing list
>  rpy...@li...
>  https://lists.sourceforge.net/lists/listinfo/rpy-list
>