Skip to content

Conversation

@pprudhvi
Copy link
Contributor

No description provided.

@pprudhvi
Copy link
Contributor Author

@pitrou

@fsaintjacques
Copy link
Contributor

Can you describe what was the issue?

@wesm
Copy link
Member

wesm commented Sep 18, 2019

Seems like the mimalloc allocator interacts badly with the JVM in some way.


if [ "$DISTRO_CODENAME" != "xenial" ]; then
CMAKE_COMMON_FLAGS="$CMAKE_COMMON_FLAGS -DARROW_MIMALLOC=ON"
fi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is definitely a hack. Can you instead add an option to toggle on/off mimalloc from .travis.yml?

Copy link
Contributor Author

@pprudhvi pprudhvi Sep 19, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated. I'm explicitly setting ARROW_TRAVIS_MIMALLOC=1 for other jobs which also build cpp lib.

@pravindra
Copy link
Contributor

@pprudhvi can you add the stack from the coredump (for the mimalloc case) in the jira ?

Copy link
Member

@wesm wesm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. Thanks for adding the backtrace in the JIRA

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.

4 participants