0 Members and 3 Guests are viewing this topic.
I compiled an Axe program so it would output an Application, but I didn't had enough archive. Naturally, it error'd. Then I found out with Calcsys it created an unnamed, 0xC6050500 byte (3 GB?) application in the archive. Now the Arc Free counter in 2nd+MEM is stuck to 0 bytes left. And I can't see it there and delete it, due of its lack of a name.Is it a bug? If not, feel free to move this post somewhere else. Anyway, it's freaking weird.
Quote from: juju2143 on February 15, 2011, 08:35:53 pmI compiled an Axe program so it would output an Application, but I didn't had enough archive. Naturally, it error'd. Then I found out with Calcsys it created an unnamed, 0xC6050500 byte (3 GB?) application in the archive. Now the Arc Free counter in 2nd+MEM is stuck to 0 bytes left. And I can't see it there and delete it, due of its lack of a name.Is it a bug? If not, feel free to move this post somewhere else. Anyway, it's freaking weird.Yeah, this is a serious bug. Having insufficient space should not destroy your calculator's memory. Axe should check the amount of space required to write the app, and then refuse to write it if space was insufficent.In the meantime, to get your memory back, try a Garbage Collect. If that doesn't work, do a Mem Clear.
Yeah I agree with Compynerd. Sometimes we don,t expect to run out of memory too. Also what's with the 3 GB app thing juju? (on IRC)
I found a bug:If you use Bitmap(, it doesnt show up good in an application. It shows up a randomly-filled square with the size of the picture.Is this a known bug?Else, this is version 0.4.8