Skip to content
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

segmentation faults when splitratio = 0.5 #99

Open
colleenchan opened this issue Apr 18, 2023 · 0 comments
Open

segmentation faults when splitratio = 0.5 #99

colleenchan opened this issue Apr 18, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@colleenchan
Copy link
Collaborator

When tuning a random forest using the caret package, segmentation faults occur often when splitratio = 0.5.

For a reproducible example, see: https://github.com/forestry-labs/GI-Collaboration/blob/main/code/3-Modeling/3.2-runPipeline.R

A segfault will occur with the parameters that are currently set:

dataset = "ehrbase"
estimator = "randomforest"
predictor = estimator
seed = 101
force = 0
embedding_dict = NULL
vi = 0

When running in a bash script, the error message would look something like:

  • Fold7.Rep1: mtry=12, nodesizeStrictSpl=2, ntree=500, splitratio=0.5521
  • Fold7.Rep1: mtry=12, nodesizeStrictSpl=4, ntree=500, splitratio=0.5000
    mtry nodesizeStrictSpl ntree splitratio
    4 12 4 500 0.5

*** caught segfault ***
address (nil), cause 'memory not mapped'

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

*** caught segfault ***
address (nil), cause 'memory not mapped'

*** caught segfault ***
address (nil), cause 'unknown'

*** caught segfault ***

*** caught segfault ***
address (nil), cause 'memory not mapped'

*** caught segfault ***
address (nil), cause 'memory not mapped'

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

*** caught segfault ***
address (nil), cause 'memory not mapped'

*** caught segfault ***
address (nil), cause 'memory not mapped'

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

*** caught segfault ***
address (nil), cause 'memory not mapped'
Error: no more error handlers available (recursive errors?); invoking 'abort' restart

*** caught segfault ***
address (nil), cause 'memory not mapped'

*** caught segfault ***
address (nil), cause 'unknown'
An irrecoverable exception occurred. R is aborting now ...
An irrecoverable exception occurred. R is aborting now ...

@petrovicboban petrovicboban added the bug Something isn't working label May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants