Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

memleax crashes the monitored process too - using version 1.1.1-1 #45

Open
lnaras1978 opened this issue Jan 2, 2019 · 10 comments
Open

memleax crashes the monitored process too - using version 1.1.1-1 #45

lnaras1978 opened this issue Jan 2, 2019 · 10 comments

Comments

@lnaras1978
Copy link

lnaras1978 commented Jan 2, 2019 •
edited
Loading

Hi,

I have been trying to use memleax. Am observing the problem of memleax crashes the targetted/monitored process also after few repetitions of starting and killing the memleax using CTRL+C
I have gone thru the discussions in this regard and suggestion to use version 1.1.1-1 but still seeing the issue.

Please let me know if you have any input in this regard. Following are my system details.

Linux OS10 4.9.110 #1 SMP Debian 4.9.110-3+deb9u4 x86_64
@lnaras1978
Copy link
Author

I saw the following error in console rarely.

Error in open /proc/pid/maps: No such file or directory

@WuBingzheng
Copy link
Owner

There are still some bugs that you can found in issue list.
They are all about multi-thread.

As said in README, memleax is complex and I do not maintain it any more.
While you may try my another tool libleax to debug memory leak, which is much simpler.

If you still prefer memleax, please let me know. Thanks.

@lnaras1978
Copy link
Author

lnaras1978 commented Jan 28, 2019 via email

@lnaras1978
Copy link
Author

Hi,

Thanks for the reply. Looks like we are hitting one of the following issues in a multithreaded environment. Where the memleax crashes the monitored process too. We are still interested in the current implementation, would like to know if you have any quick patch for the issue so that we shall try and get back.

#6

#24

Regards,
Narasimhan

@WuBingzheng
Copy link
Owner

Sorry, there is no patch. Because it's too complicated, and I think libleak it's better.

Would you like tell me why you prefer memleax to libleak?

@raghavb1979
Copy link

Hi,

I am using this memleax tool in an jvm environment. I monitored the java process for native memory leak detection but the the target process crashing. I need this memleax tool because this tool is excellent in attaching to the process and identifying the memleak and I tried valgrind it is not working. Now memleax is also not working and with libleak.so the jvm not starting at all. Kindly help in fixing the problem in memleax tool it will be more more helpful. Stress is building in office. Kindly help in fixing the problem of target process crash. still existing in 1.1.1 as well. Kindly let me know what log you need to solve the problem.

@WuBingzheng
Copy link
Owner

libleak is much simpler than memleax. If libleak can not work with jvm, it's likely than memleak can not work with jvm neither even if the current bug fixed.

Whose memory leak do you want to detect? Is jvm itself, or your java programs running on jvm?

@WuBingzheng
Copy link
Owner

It's too hard to fix memleax's bug. I am not able to fix it.
If I could, I would not write libleak.

@raghavb1979
Copy link

raghavb1979 commented Dec 17, 2019 via email

@WuBingzheng
Copy link
Owner

Both memleax and libleak are useful if you can not modify the target program's source code.

If you can modify it, you may use hooks for malloc.

memleak and libleak may be too naive to work with complex programs such as JVM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@WuBingzheng @raghavb1979 @lnaras1978