Skip to content

Conversation

@alex85k
Copy link
Contributor

@alex85k alex85k commented Aug 12, 2014

After d1b6c5e#diff-a4a10b448709d2cc5dc0c85fb36a2b1c
the RAM cache size can be zero, but ram_cache_nodes_set_sparse function often accesses sparseBlock[0]. It gives serious memory access errors and failures during testing (detected with Intel Inspector XE when fixing Windows builds #17 ).

I am not sure the proposed fix is the best solution, but something should be done with this error.

After osm2pgsql-dev@d1b6c5e#diff-a4a10b448709d2cc5dc0c85fb36a2b1c
the RAM cache size can be zero, but ``am_cache_nodes_set_sparse`` often accesses ``sparseBlock[0]``. It gives serious memory access erros and failures during testing (detected with Intel Inspector XE when fixing Windows builds osm2pgsql-dev#17 ).

I am not sure the proposed fix is the best solution, but something should be done with this error.
apmon added a commit that referenced this pull request Sep 9, 2014
@apmon apmon merged commit bf50103 into osm2pgsql-dev:master Sep 9, 2014
@alex85k alex85k deleted the patch-1 branch October 15, 2015 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants