JuliaInterop / JuliaInterop/JavaCall.jl
Profiling broken after calling JavaCall.init()
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Julia
- Stars
- 125
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
After calling JavaCall.init(), profiler does not collect any samples anymore.
--
Julia 0.6.2, JavaCall 0.5.2, Ubuntu 16.04
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with Julia 0.6.2, JavaCall 0.5.2, and Ubuntu 16.04 by comparing profiler behavior before and after JavaCall.init(). Start by tracing JavaCall.init() and the profiler interaction; done when profiling continues to collect samples after initialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, julia
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100