In the devkit, are loading files larger than 1 mb possible?

[elkaamee326]

In the userkit, when I tried to load a 2.63 mb file, it just displayed, "CPU exception: 0XD." In the dev kit, is this issue fixed? Also, is the exception a bitmap problem, File System, or is it from the Bitmap ctor? My file worked when the size was 640x480 (and that size was 900kb) but when I changed it to 720x1280, it showed that exception. BMP details: 24bpp BGR, 720x1280 and 2.63 mb file. Is the larger than 1mb issue fixed in the dev kit? Thx.

This is the VM output:

This was when I put a try and catch block.

[quajak]

The problem is a file system one and has not been fixed in the devkit. The problem does not appear directly at 1mb but also for files slightly smaller.

[elkaamee326]

Could this be the problem? long xMaxReadableBytes = mDirectoryEntry.mSize - mPosition; Also, what is DirectoryEntry.mSize and what is it for?

[quajak]

A DirectoryEntry doesnt necessarily mean that its a Directory, it can also still be a File on the disk. mSize is the size of the File/Directory and therefore limits how much can still be read. Therefore, I don' think long xMaxReadableBytes = mDirectoryEntry.mSize - mPosition is the problem, since we limit how much more we can read by how there is in the file and how much we have read already.

[elkaamee326]

Could it be a memory problem? Because when I loaded a 0.98mb file, it loaded the .bmp fine, except at the top of the image it showed a bunch of random pixels. Could this be because it doesn't have a sufficient amount of RAM to store / draw those last few pixels? (The area of random pixels (length and width) was approximately an array of 30x640)...

[elkaamee326]

Also, when I tried to load a 2.63mb file with the devkit, it displayed "CPU Exception x05" and not x0D. Do you know what each of these error codes mean?

[quajak]

Could it be a memory problem? Because when I loaded a 0.98mb file, it loaded the .bmp fine, except at the top of the image it showed a bunch of random pixels. Could this be because it doesn't have a sufficient amount of RAM to store / draw those last few pixels? (The area of random pixels (length and width) was approximately an array of 30x640)...

I would expect cosmos to not run into memory issues quiet that quickly but thats certainly possible. If you create a bitmap with just a height and width of a similar size and fill the color array with some values, can you display it correctly? The 2.63mb case most likely means the image did overflow into code, which means that random stuff happens and we crash and burn in some way.

[elkaamee326]

I am currently working on a project, which its GUI is based off of this: https://github.com/nifanfa/Cosmos-GUI-Sample

but apparently, I set the screen resolution to 1360x768 with a background image.

As you can see the fps is at 8 (when it is supposed to be at 30. This causes a big cursor lag) and for some reason when I load too many apps the VM crashes.
Also, the background image was loaded by taking a .bmp file and converting it into a byte array and when I loaded it through a byte array it worked, but for some reason the cursor movement was very slow. I even tried increasing VRAM but it didn't really benefit as well as RAM too. What is the problem and can this be resolved? Also, I know what is the main cause of this problem (the 22.3 mb image byte array compiled into a .dll to allow the IDE to not crash. When the .dll was compiled, it was only 3.56 mb) Is there anything I can do, or anything that is required? Thanks very much, any reply is appreciated :)

[elkaamee326]

Also, if the memory ran out then why if I try to increase ram or vram it isn't very useful and it doesn't resolve the cursor lag?

[quajak]

The Garbage Collector will extend the Memory Manager to automatically free memory again. Until that it done, using the new Memory Manager does not make sense.

[elkaamee326]

Once implemented, will the memory manager (Including GC) help stop the lag for this project and also, what did you mean by memory? Did you mean the memory that is assigned to the graphics card aka VRAM? Or did you mean the System RAM that cosmos uses for the CPU and the main hardware? Or the memory that is dedicated to Cosmos (code defined and not virtual machine defined if present). Lastly, will having a GC help with performance too when cleaning up garbage and anything that is created for everytime that the graphics card updates? Would this be a possible solution without changing the screen resolution. Thank you for all the help :)

[quajak]

The GC will not fix the lag you are experiencing but will stop the terminal freeze. The only way you will get rid of the freezes is by optimizing your graphics code.

[elkaamee326]

Okay, thanks :)