|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« "And the Oscar goes to bug 6635!" | Main | Search and ye shall find »
Though Carbide C++ is a C++ development environment, I am sure that many developers develop Java apps for s60 as well. We had a weird problem when reading a large file into a java byte array. Despite the fact that I had 1 GB allocated to Java VM, I was getting 'Out of memory' exception when trying to create 100MB byte array. The solution to this problem is to use a MappedMemoryBuffer class from nio package. It doesn't allocate the memory but instead maps the memory buffer to the file in the file systems. It is even more useful for the s60 development, since the available memory on the devices is really small. It is nice to use nio APIs for s60 Java development!