Databases
StackOverflow2013
Postsdbo
POdelete memory allocated to a byte array
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdelete memory allocated to a byte array
    primarykey
    data
    text
    <p>I am receiving records in while loop at a socket server. where each records has a msg type followed by message length and actual message content. </p> <p>The problem is that since I get around a million records and each record has a record size of 277 bytes. So, after around 40000 records, I get OutOfMemory error. The code flow looks something like this:</p> <pre><code>while (true) { msgType = dIn.readByte(); int msgIntType = msgType &amp; 0xff; // get message length int msgIntLen = dIn.readInt(); if (msgIntLen != 0) { msgContent = new byte[msgIntLen]; switch(msgIntType) { case 4: //case MSG_DATA: // MSG_DATA recordCount++; processData(msgContent); if (recordCount == 2000) { sendACK(dOut, msgIntType); logger.info("sent ACK for MSG_DATA"); recordCount = 0; } break; } </code></pre> <p>I resolved the OutOfMemory issue by explicitly calling System.gc() after sending ACK after every 2000 records processed and now it works perfectly fine and able to handle 1 million records without any error in less than 10 minutes. The modified code for case statement for calling System.gc() looks like:</p> <pre><code> case 4: //case MSG_DATA: // MSG_DATA recordCount++; processData(msgContent); if (recordCount == 2000) { sendACK(dOut, msgIntType); logger.info("sent ACK for MSG_DATA"); recordCount = 0; System.gc(); } break; </code></pre> <p>But I read here on some other posts that calling System.gc() is not a good design approach ? Is it so ? If yes, could you guys suggest me some other way to get rid of this OutOfMemory error ?</p> <p>Thanks in advance -JJ</p> <p>EDIT: logic for processData():</p> <pre><code>public void processData(byte[] msgContent) throws Exception { InputStreamReader inp = new InputStreamReader( new ByteArrayInputStream(msgContent)); BufferedReader br = null; try { br = new BufferedReader(inp); String line; while ((line = br.readLine()) != null) { process each line . } } catch (Exception e) { logger.error("exception in " + Utils.getExecutingMethodName(e) + " :" + e.getMessage()); } finally { try { if (br != null) br.close(); } catch (IOException e) { logger.error("Error: " + e); } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser656189
    1. USuser656189
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POdelete memory allocated to a byte array
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POdelete memory allocated to a byte array
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat does `processData()` do? Is it possible it keeps a reference to the byte array somehow?
      singulars
      1. POdelete memory allocated to a byte array
      1. USmatt b
    2. COI suggest you take a heap dump of the out of memory error and analyse it. It should show wheer your memory is being held. It might point to a solution.
      singulars
      1. POdelete memory allocated to a byte array
      1. USPeter Lawrey
    3. CO@matt - just added the code.
      singulars
      1. POdelete memory allocated to a byte array
      1. USuser656189
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload