[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug classpath/42823] tcp/ip sockets read/write operations causes memory
From: |
mscott at webtechwireless dot com |
Subject: |
[Bug classpath/42823] tcp/ip sockets read/write operations causes memory leak |
Date: |
Wed, 30 Mar 2011 21:01:22 +0000 |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42823
mscott at webtechwireless dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mscott at webtechwireless
| |dot com
--- Comment #4 from mscott at webtechwireless dot com 2011-03-30 21:01:06 UTC
---
We are experiencing similiar memory leaks, not on open/close operations but on
read/write. An average of 400 bytes per message when using sockets to transmit
data between .Net client and Java service both running in Win CE.
GNU Classpath v0.97.1
JVM MySaifu 0.4.8
OS WinCE 6.0
Platform ARM4i
Each request to the java service is at least 2 packets in length (We needed to
implemnet our own flush() by padding messages with 1493 bytes to ensure that
the last bytes of our message are pushed through the layers)
We do not close connections between requests
But
When monitoring memory usage in the Win CE environment with a process
monitor/task manager we can see over time increased memory consumption.
Calcualtion of memory usage over ten, hundreds or thousands of messages shows
aproximatelyt 400 bytes per message!