Skip to content

[Bug] predict.EvoWeaver segfaults with Processors=4 #44

@ahl27

Description

@ahl27

Encountered a bug recently where predict.EvoWeaver crashes when called with larger values of Processors. I'm not sure what the cause of this is yet, but I'm going to investigate it in future.

Reproducing the bug:

library(SynExtend)
load("SomethingCrashing.RData")
predict(pw, Method=all_methods, Processors=4L)

This bug seems to occur when called with Method="ResidueMI", but I'm not convinced that the segfault is actually due to that function...could be a memory corruption error in one of the previous predictors. Resolution of this should include updating all the OpenMP calls to the new format mentioned by Erik.

Traceback:
 1: t.default(t(APCm) * colMeans(AllMIs))
 2: t(t(APCm) * colMeans(AllMIs))
 3: t(t(APCm) * colMeans(AllMIs))
 4: ResidueMISeqs(seqs1, seqs2, lookup = lookup, useColoc = useColoc,     Processors = Processors, ...)
 5: func(ew, Subset = Subset, Verbose = Verbose, MySpeciesTree = MySpeciesTree,     Processors = Processors, PretrainedModel = PretrainedModel,     NoPrediction = NoPrediction, ...)
 6: predict.EvoWeaver(pw, Method = all_methods, Verbose = FALSE,     Processors = 4L)
 7: predict(pw, Method = all_methods, Verbose = FALSE, Processors = 4L)

Possible actions:
1: abort (with core dump, if enabled)
2: normal R exit
3: exit R without saving workspace
4: exit R saving workspace

SomethingCrashing.RData.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions