New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault in rbind_all #463

Closed
hoesler opened this Issue Jun 12, 2014 · 3 comments

Comments

Projects
None yet
4 participants
@hoesler

hoesler commented Jun 12, 2014

rbind_all applied to a list of data frames with special columns like in

dfl <- data.frame(x = I(list(1:2, 1:3, 1:4)))
rbind_all(list(dfl, dfl))

results in a segfault:

Invalid memory access of location 0x0 rip=0x10a21b5a8

 *** caught segfault ***
address 0x0, cause 'memory not mapped'

Traceback:
 1: .Call("dplyr_rbind_all", PACKAGE = "dplyr", dots)
 2: rbind_all(list(dfl, dfl))

This could be related to #459.

@yasminlucero

This comment has been minimized.

yasminlucero commented Jan 6, 2015

I just ran into this.


*** caught segfault ***
address 0x20000010, cause 'memory not mapped'

Traceback:
1: .Call("dplyr_rbind_all", PACKAGE = "dplyr", dots)
2: rbind_all(data)
3: readData()
aborting ...

Segmentation fault (core dumped)

The object 'data' is a list where each element is a data.frame with 22 columns. Each data.frame in the list was produced by reading a delimited file using fread and passing this list of column classes:

class = c(rep('character', 4), rep('integer', 8), rep('numeric', 4), rep('integer', 6))

This same code runs fine on dplyr_0.2. Upgrading dplyr surfaced this issue.

I am running dplyr_0.3.0.2 and R v 3.1.2 on Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-69-generic x86_64).

@romainfrancois

This comment has been minimized.

Member

romainfrancois commented Jan 7, 2015

@yasminlucero please send us a reproducible example. Did you test with the development version ?

@yasminlucero

This comment has been minimized.

yasminlucero commented Jan 7, 2015

@romainfrancois I will, as soon as I find a moment

@lock lock bot locked as resolved and limited conversation to collaborators Jun 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.