Displaying 6 results from an estimated 6 matches for "7970512".
2017 Apr 18
3
Crash after (wrongly) applying product operator on object from LIMMA package
...plication of sweep or the product ("*") function on an LIMMA MAList
object. To my knowledge, limma does not define a "*" method for MAList
objects.
If only LIMMA is loaded but not package xlsx, the code does not crash
but rather produces an error ("Error: C stack usage 7970512 is too
close to the limit"). Loading only package rJava instead of xlsx does
also not produce the crash but the error message instead. Note that xlsx
functions are not explicitly used.
It could be reproduced on two different Linux machines running R-3.2.5,
R-3.3.0 and R-3.3.2.
Code to re...
2017 Apr 19
2
Crash after (wrongly) applying product operator on S4 object that derives from list
...g up on my own question, I found smaller example that does not
> require LIMMA:
>
> setClass("FOOCLASS",
> representation("list")
> )
> ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10)))
>
>> ma * ma$M
> Error: C stack usage 7970512 is too close to the limit
>
>> library(xlsx)
> Loading required package: rJava
> Loading required package: xlsxjars
>> ma * ma$M
> ---> Crash
>
> xlsx seems to act like a catalyst here, with the product operator
> running in a deep nested iteration, exhausting th...
2017 Apr 24
2
Crash after (wrongly) applying product operator on object from LIMMA package
...up on my own question, I found smaller example that does not
> require LIMMA:
>
> setClass("FOOCLASS",
> representation("list")
> )
> ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10)))
>
> > ma * ma$M
> Error: C stack usage 7970512 is too close to the limit
>
> > library(xlsx)
> Loading required package: rJava
> Loading required package: xlsxjars
> > ma * ma$M
> ---> Crash
>
> xlsx seems to act like a catalyst here, with the product operator running
> in a deep nested iteration, exhausting...
2017 Apr 19
0
Crash after (wrongly) applying product operator on object from LIMMA package
Hi,
following up on my own question, I found smaller example that does not
require LIMMA:
setClass("FOOCLASS",
representation("list")
)
ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10)))
> ma * ma$M
Error: C stack usage 7970512 is too close to the limit
> library(xlsx)
Loading required package: rJava
Loading required package: xlsxjars
> ma * ma$M
---> Crash
xlsx seems to act like a catalyst here, with the product operator
running in a deep nested iteration, exhausting the stack. Valgrind shows
thousands of...
2017 Apr 19
0
Crash after (wrongly) applying product operator on S4 object that derives from list
...ple that does not
>> require LIMMA:
>>
>> setClass("FOOCLASS",
>> representation("list")
>> )
>> ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10)))
>>
>>> ma * ma$M
>>
>> Error: C stack usage 7970512 is too close to the limit
>>
>>> library(xlsx)
>>
>> Loading required package: rJava
>> Loading required package: xlsxjars
>>>
>>> ma * ma$M
>>
>> ---> Crash
>>
>> xlsx seems to act like a catalyst here, with the product...
2017 Apr 24
0
Crash after (wrongly) applying product operator on object from LIMMA package
...und smaller example that does
> not require LIMMA:
>
> setClass("FOOCLASS",
> representation("list")
> )
> ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10)))
>
> > ma * ma$M
> Error: C stack usage 7970512 is too close to the limit
>
> > library(xlsx)
> Loading required package: rJava
> Loading required package: xlsxjars
> > ma * ma$M
> ---> Crash
>
> xlsx seems to act like a catalyst here, with the product operator
> running in a deep n...