Hi Martin,
Thank you for going so deep. I tried
R -d "valgrind --leak-check=full --track-origins=yes" -f plotInteractionData.R
to locate the exact line where initialed the possible leak.
Is there any other possibility that killed the process and did not leave any
error log information?
I followed these steps, more or less, to configure and use valgrind on the
Bioconductor docker image.
https://gist.github.com/mtmorgan/77f9d92d81830eeb7f254809b445874d
For this particular use I
- added the valgrind system dependency
- installed trackViewer and it's 'Suggests' dependencies in
Hi Herv�,
Thank you for the information. I will try to figure out.
Jianhong.
From: Herv� Pag�s
Sent: Wednesday, April 7, 2021 1:54 AM
To: Jianhong Ou, Ph.D. ; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] Ask for help to debug the error on riesling1
Hi
Hi Jianhong,
Memory leaks and other memory errors are bugs in native code that often
exist on all platforms but typically manifest themselves in different
ways depending on the platform where it runs. Running your code thru a
tool like Valgrind should reveal these problems even if you do this
Hi,
The trackViewer package got error on Windows Server since version 1.27.4. I am
totally lost to figure it out by myself. The current error message listed in
building system is:
* creating vignettes ... ERROR
--- re-building 'changeTracksStyles.Rmd' using rmarkdown
--- finished re-building
