jinxuan / sparsehash

Automatically exported from code.google.com/p/sparsehash
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Dense_hash_map - Assertion `table' failed. #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. not sure yet, but every time I used dense_hash_map with a large dataset, it 
occurred.

What is the expected output? What do you see instead?
It seems it could not create a new table?

What version of the product are you using? On what operating system?
the current version on Ubuntu

Please provide any additional information below.
I am using a transaction dataset, including more than 40 000 transactions. For 
each one, I will set up a map. It could proceed for more than 30 000 
transactions, but have problem with one, and it stopped. Don't know what 
assertion(table) failed means...
./google/sparsehash/densehashtable.h:479: void google::dense_hashtable<Value, 
Key, HashFcn, ExtractKey, EqualKey, Alloc>::expand_array(size_t, 
google::true_type) [with Value = std::pair<const char* const, int>, Key = const 
char*, HashFcn = __gnu_cxx::hash<const char*>, ExtractKey = 
google::dense_hash_map<const char*, int, __gnu_cxx::hash<const char*>, 
Chars_Comp, std::allocator<int> >::SelectKey, EqualKey = Chars_Comp, Alloc = 
std::allocator<int>]: Assertion `table' failed.

Original issue reported on code.google.com by xzhao.u...@gmail.com on 1 Apr 2011 at 3:33

GoogleCodeExporter commented 9 years ago
Try downloading the most recent version of sparsehash and see if the problem 
persists.  I'm going to close this bug Invalid since it's against an older 
version of sparsehash (expand_array no longer exists), but feel free to reopen 
it, with appropriate new details, if you can reproduce against sparsehash 1.10

Original comment by csilv...@gmail.com on 6 Apr 2011 at 4:24

GoogleCodeExporter commented 9 years ago
I`ve catch this problem on 1.10 version

Original comment by zaharov...@gmail.com on 30 May 2011 at 2:14

GoogleCodeExporter commented 9 years ago
Zaharov..., your problem could be a different bug.  Usually !table means you 
are out of memory.  (The original report did not fit this profile.)  Is that 
possibly what is happening in your case?

Original comment by csilv...@gmail.com on 31 May 2011 at 10:27

GoogleCodeExporter commented 9 years ago
01.06.2011 02:33, google-sparsehash@googlecode.com пишет:

Im sorry, its realy not a bug. There was an refactoring application 
problem: set_empty_key() is not being called before dense_hash_set 
insertion..

Original comment by zaharov...@gmail.com on 3 Jun 2011 at 10:46