-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
We've seen glibc complaints twice now – it's with lz4, I'm wondering if there's a problem there.
Here's the error and CONFIG.
** glibc detected *** ./t: double free or corruption (!prev): 0x0000000002874240 *** t: cursor.insert: WT_NOTFOUND: item not found *** glibc detected *** ./t: double free or corruption (!prev): 0x0000000002874240 *** ############################################ # RUN PARAMETERS ############################################ abort=0 auto_throttle=1 firstfit=0 bitcnt=2 bloom=1 bloom_bit_count=40 bloom_hash_count=24 bloom_oldest=0 cache=60 checkpoints=1 checksum=uncompressed chunk_size=7 compaction=0 compression=lz4 data_extend=0 data_source=file delete_pct=25 dictionary=0 evict_max=4 file_type=variable-length column-store backups=0 huffman_key=0 huffman_value=0 insert_pct=34 internal_key_truncation=1 internal_page_max=13 isolation=read-committed key_gap=17 key_max=76 key_min=32 leak_memory=0 leaf_page_max=10 logging=0 logging_archive=1 logging_prealloc=1 lsm_worker_threads=4 merge_max=17 mmap=1 ops=100000 prefix_compression=1 prefix_compression_min=5 repeat_data_pct=65 reverse=0 rows=100000 runs=100 split_pct=48 statistics=0 statistics_server=0 threads=31 timer=20 value_max=1916 value_min=4 wiredtiger_config= write_pct=72 ############################################
- is depended on by
-
SERVER-18270 WiredTiger changes for MongoDB 3.1.3
- Closed
- links to