3. What actually happened?
···
[vg rna] Parsing graph file ...
[vg rna] Graph parsed in 8.25311 seconds, 1.80941 GB
[vg rna] Adding transcript splice-junctions and exon boundaries to graph ...
[vg rna] 14015 transcripts parsed and graph augmented in 67.9664 seconds, 14.4324 GB
[vg rna] Chopping long nodes ...
terminate called after throwing an instance of 'std::out_of_range'
what(): at: key not present
ERROR: Signal 6 occurred. VG has crashed. Visit https://github.com/vgteam/vg/issues/new/choose to report a bug.
Stack trace path: /tmp/vg_crash_Ko8HSO/stacktrace.txt
Please include the stack trace file in your bug report!
···
4. If you got a line like Stack trace path: /somewhere/on/your/computer/stacktrace.txt, please copy-paste the contents of that file here:
Crash report for vg v1.42.0 "Obolo"
Stack trace (most recent call last):
#17 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x602fa4, in _start
#16 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1fbe506, in __libc_start_main
#15 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1fbcca9, in __libc_start_call_main
#14 Object "/data13/kongqq/software/env/vg/bin/vg", at 0xdc215b, in vg::subcommand::Subcommand::operator()(int, char**) const
#13 Object "/data13/kongqq/software/env/vg/bin/vg", at 0xd947c0, in main_rna(int, char**)
#12 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x12e864b, in vg::Transcriptome::chop_nodes(unsigned int)
#11 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x175d585, in bdsg::HashGraph::for_each_handle_impl(std::function<bool (handlegraph::handle_t const&)> const&, bool) const
#10 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x12f2f7f, in _ZNSt17_Function_handlerIFbRKN11handlegraph8handle_tEEZNS0_20BoolReturningWrapperIZN2vg13Transcriptome10chop_nodesEjEUlS3_E_Lb0EE4wrapERKS8_EUlDpOT_E_E9_M_invokeERKSt9_Any_dataS3_
#9 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1762474, in bdsg::HashGraph::get_length(handlegraph::handle_t const&) const
#8 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x176bd4e, in spp::sparse_hash_map<long long, bdsg::HashGraph::node_t, bdsg::wang_hash<long long, void>, std::equal_to<long long>, spp::libc_allocator<std::pair<long long const, bdsg::HashGraph::node_t> > >::at(long long const&) const
#7 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x42b188, in void spp::throw_exception<std::out_of_range>(std::out_of_range const&)
#6 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1ef6958, in __cxa_throw
#5 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1ef67f6, in std::terminate()
#4 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1ef678b, in __cxxabiv1::__terminate(void (*)())
#3 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x5d0ad9, in __gnu_cxx::__verbose_terminate_handler() [clone .cold]
#2 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x5d3221, in abort
#1 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x1fd56e5, in raise
#0 Object "/data13/kongqq/software/env/vg/bin/vg", at 0x20020ec, in __pthread_kill
I tried the same command with other chromosomes and they all worked fine, but I don't know why there is such a problem in Chr3 and Chr4.
5. What does running vg version say?
vg version v1.42.0 "Obolo"
Compiled with g++ (Ubuntu 11.2.0-19ubuntu1) 11.2.0 on Linux
Linked against libstd++ 20220324
Built by ubuntu@ip-172-31-12-246
Hello, I want to construct a pantranscriptome with two haplotypes in a diploid. 1.What I have done
Works fine 2. What data and command can the vg dev team use to make the problem happen?
3. What actually happened? ··· [vg rna] Parsing graph file ... [vg rna] Graph parsed in 8.25311 seconds, 1.80941 GB [vg rna] Adding transcript splice-junctions and exon boundaries to graph ... [vg rna] 14015 transcripts parsed and graph augmented in 67.9664 seconds, 14.4324 GB [vg rna] Chopping long nodes ... terminate called after throwing an instance of 'std::out_of_range' what(): at: key not present ERROR: Signal 6 occurred. VG has crashed. Visit https://github.com/vgteam/vg/issues/new/choose to report a bug. Stack trace path: /tmp/vg_crash_Ko8HSO/stacktrace.txt Please include the stack trace file in your bug report! ···
4. If you got a line like
Stack trace path: /somewhere/on/your/computer/stacktrace.txt
, please copy-paste the contents of that file here:I tried the same command with other chromosomes and they all worked fine, but I don't know why there is such a problem in Chr3 and Chr4.
5. What does running
vg version
say?My gff files