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

Segfault during commit #141

Closed
fulmicoton opened this issue May 11, 2017 · 1 comment
Closed

Segfault during commit #141

fulmicoton opened this issue May 11, 2017 · 1 comment
Labels

Comments

@fulmicoton
Copy link
Collaborator

As reported by @aabstain .

akss:resources akss$ RUST_BACKTRACE=1 cargo run Compiling tantivy_sandbox v0.1.0 (file:///Users/akss/programming/rust/tantivitySandbox) Finished dev [unoptimized + debuginfo] target(s) in 3.70 secs Running/Users/akss/programming/rust/tantivitySandbox/target/debug/tantivy_sandbox 10000 thread 'indexing thread 0 for gen 0' panicked at 'index out of bounds: the len is 3 but the index is 16777216', /Users/travis/build/rust-lang/rust/src/libcollections/vec.rs:1490 stack backtrace: 0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace 1: std::panicking::default_hook::{{closure}} 2: std::panicking::default_hook 3: std::panicking::rust_panic_with_hook 4: std::panicking::begin_panic 5: std::panicking::begin_panic_fmt 6: rust_begin_unwind 7: core::panicking::panic_fmt 8: core::panicking::panic_bounds_check 9: <collections::vec::Vec<T> as core::ops::Index<usize>>::index 10: tantivy::schema::schema::Schema::get_field_entry 11: tantivy::postings::serializer::PostingsSerializer::load_indexing_options 12: tantivy::postings::serializer::PostingsSerializer::new_term 13: <tantivy::postings::postings_writer::SpecializedPostingsWriter<'a, Rec> as tantivy::postings::postings_writer::PostingsWriter>::serialize 14: tantivy::indexer::segment_writer::write 15: tantivy::indexer::segment_writer::SegmentWriter::finalize 16: tantivy::indexer::index_writer::index_documents 17: tantivy::indexer::index_writer::IndexWriter::add_indexing_worker::{{closure}} 18: <std::panic::AssertUnwindSafe<F> as core::ops::FnOnce<()>>::call_once 19: std::panicking::try::do_call 20: __rust_maybe_catch_panic 21: std::panicking::try 22: std::panic::catch_unwind 23: std::thread::Builder::spawn::{{closure}} 24: <F as alloc::boxed::FnBox<A>>::call_box 25: std::sys::imp::thread::Thread::new::thread_start 26: _pthread_body 27: _pthread_start

@fulmicoton fulmicoton added the bug label May 11, 2017
@fulmicoton fulmicoton changed the title Regression in 0.3.1 Regression in 0.3.1, segfault during commit May 11, 2017
@fulmicoton fulmicoton changed the title Regression in 0.3.1, segfault during commit Segfault during commit May 11, 2017
@fulmicoton
Copy link
Collaborator Author

The bug is in master, not in 0.3.1.

It has been introduced when I changed the way we serialize the field part of the Term.

fulmicoton added a commit that referenced this issue May 11, 2017
Also.

Cleaned up the code to make sure that the logic
is only in one place.
Removed allocate_vec

Closes #141
Closes #139
Closes #142
Closes #138
fulmicoton added a commit that referenced this issue May 11, 2017
Also.

Cleaned up the code to make sure that the logic
is only in one place.
Removed allocate_vec

Closes #141
Closes #139
Closes #142
Closes #138
fulmicoton added a commit that referenced this issue May 11, 2017
Also.

Cleaned up the code to make sure that the logic
is only in one place.
Removed allocate_vec

Closes #141
Closes #139
Closes #142
Closes #138
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant