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.

Sign up for GitHub

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

Jump to bottom

crash on background compaction #427

Closed
ghost opened this issue Nov 16, 2016 · 2 comments
Closed

crash on background compaction #427

ghost opened this issue Nov 16, 2016 · 2 comments
Labels
bug

Comments

@ghost
Copy link

ghost commented Nov 16, 2016

image
above pic shows backtrace in my program. using leveldb as static library. In case pic does not display, type the backtrace below
leveldb::DBImpl::MemTableIterator::key() const()
leveldb::DBImpl::BuildTable()
leveldb::DBImpl::WriteLevel0Table()
leveldb::DBImpl::CompactMemeTable()
leveldb::DBImpl::BackgroundCompaction()
leveldb::DBImpl::BackgroundCall()
@cmumford
Copy link
Contributor

cmumford commented Jan 4, 2017

You're using an in-memory database. Are you sure not running out of memory? Do you have a reproduction?

@cmumford cmumford added the bug label Jan 4, 2017
@cmumford
Copy link
Contributor

Closing due to lack of feedback. Please reopen if this can be reproduced.

maochongxin pushed a commit to maochongxin/leveldb that referenced this issue Jul 21, 2022
@LebedevRI @dominichamon
Tooling: generate_difference_report(): show old/new for both values (g…
d474450 
…oogle#427)

While the percentages are displayed for both of the columns,
the old/new values are only displayed for the second column,
for the CPU time. And the column is not even spelled out.

In cases where b->UseRealTime(); is used, this is at the
very least highly confusing. So why don't we just
display both the old/new for both the columns?

Fixes google#425
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cmumford