out of memory exception

[tvgece]

I am trying to read a 2mb file into a memory and then send that file to web server. But I am getting out of memory exception

  FileConnection fileConn = (FileConnection)Connector.open("file:///" + pictureURI.getString(), Connector.READ);
     InputStream fis = fileConn.openInputStream();
     long overallSize = fileConn.fileSize();

     int chunkSize = 2048;
     int length = 0;
     while (length < overallSize)
     {

        byte[] data = new byte[chunkSize];
        int readAmount = fis.read(data, 0, chunkSize);
        byte[] newImageData = new byte[rawImage.length + chunkSize];
        System.arraycopy(rawImage, 0, newImageData, 0, length);
        System.arraycopy(data, 0, newImageData, length, readAmount);
        rawImage = newImageData;
        length += readAmount;

     }
       fis.close();
        fileConn.close();

500kb files are uploading. What could be the reason? Please shed a light on this.

I tried this also in loop but no use, System.gc();

Thanks in advance.

[r2j7]

Hello tvgece,

and welcome to Nokia Developer Discussion Boards!

A question to start with, which device are you using for your application?

Also, does this happen only during uploading? What about without uploading?

Also you might want to check this article on memory usage for images on Nokia Developer Wiki: http://www.developer.nokia.com/Commu...y_Usage_Images

Regards,
r2j7

[tvgece]

Hi,

I am using Nokia X2-01(s40).

I tried different methods, loading the file in to memory and then sent those data. (loading into memory worked), but when I initiated the upload process, it giving error.

Then I tried fetching 1024 bytes into a buffer and sent those, repeated till the end of file, but its still giving same error after 60% of the upload.

Is there any limit for uploading in this device? or any memory limit?

Thanks in advance

[r2j7]

Hello tvgece,

Nokia X2-01 has heap limitation of 2 MB which sets limitations on how much memory is available for MIDlet to handle runtime operations: when too much memory is used during operation than there is available in the heap then that usually leads to the outcome which you are experiencing.

Can you try running the application on a Series 40 SDK emulator and monitor the memory consumption via Diagnostics window in order to see what happens in the application when this happens?

Regards,
r2j7