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

Core error when running outriger psi #87

Open
cfbuenabadn opened this issue Aug 28, 2017 · 0 comments
Open

Core error when running outriger psi #87

cfbuenabadn opened this issue Aug 28, 2017 · 0 comments

Comments

@cfbuenabadn
Copy link

cfbuenabadn commented Aug 28, 2017

Hello!

I get an error when I try o run outrigger psi that seems to come from C code. Outrigger index and validate work fine, but when I attempt to run psi I get the following error:

(outrigger-env) /path/to/my/expedition/files/$ outrigger psi
2017-08-28 10:51:09     Creating folder ./outrigger_output ...
2017-08-28 10:51:09             Done.
2017-08-28 10:51:09     Creating folder ./outrigger_output/psi ...
2017-08-28 10:51:09             Done.
2017-08-28 10:51:09     Found compiled junction reads file in ./outrigger_output/junctions/reads.csv and reading it in ...
*** Error in `/path/to/my/anaconda3/envs/outrigger-env/bin/python': free(): invalid pointer: 0x00007fc1cfe471c4 ***
Aborted (core dumped)

I get this error simply by running outrigger following the steps indicated on the instructions. As I mentioned earlier, index and validate seem to work normally and produce the expected outputs.

I have Anaconda 4.3.14 installed with python 3.6.0 (that's what I used when installing outrigger). However, I've noticed that the python version on the outrigger environment (/path/to/my/anaconda3/envs/outrigger-env/bin/python) is 3.5.4 instead (I ignore the reason for this).

All this happens with outrigger 1.1.1, running on a server with Ubuntu 14.04.5 LTS.

Thank you for your help,
Carlos

UPDATE: This might be a memory issue. I was working with >600 SJ files when it crashed. I tried again using just a few and it worked as expected. Is it possible to parallelize the process to see if it solves the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant