Skip to content
New issue

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

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

Already on GitHub? # to your account

Memory not reseting after downloading a (large) file #95

Open
Bence77 opened this issue Sep 29, 2016 · 6 comments
Open

Memory not reseting after downloading a (large) file #95

Bence77 opened this issue Sep 29, 2016 · 6 comments

Comments

@Bence77
Copy link

Bence77 commented Sep 29, 2016

I use Mockey to download large files with proxy (100MB+), and I noticed, that after each download, the memory is not 'reseting', so if I download a 100MB file, then the memory usage jumps up with ~200-300MB, and on another download, more 200-300MB is used by Mockey, then after some time, it shows that there is not enough java heap space.
I just picked a link to test: http://ovh.net/files/1Gb.dat
So locally the url: 127.0.0.1:8080/service/http://ovh.net/files/1Gb.dat

@clafonta
Copy link
Owner

Mockey is recording the transactions; that is the reason memory continues to climb up. See the 'History' tab and 'clear history' to purge the records. Let me know if that works.

@Bence77
Copy link
Author

Bence77 commented Sep 30, 2016

I cleared the history, but the program is still use the same (high) amount of memory. Normally the program use ~100MB memory, when I start the download, it use 300, and when it finishes, it jump to 700. In the next download while downloading 900, and after it 1300, etc... In the history if i click to the view, the memory usage jumps to 5GB, and my browser is frozen.

@clafonta
Copy link
Owner

I'll looked into it further.

@clafonta
Copy link
Owner

FYI, this is difficult to fix. Here's what I see when I run against a large data file: the app' hits memory heap exception and I believe garbage collection recovers very little memory in each run.

@Bence77
Copy link
Author

Bence77 commented Oct 11, 2016

Is it necessary to store the file? I don't think, that anyone wanna look inside into a (large) file from the ui, it can be enough to store only the regular informations about it. Or the problem occurs outside of the history?

@clafonta
Copy link
Owner

Unfortunately, the problem happens outside the history. I know where it happens - during read-in after a few tries. I have a few more things to try.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants