Lemur editor HUGE memory bug

[m127]

So I have been porting my original Lemur templates to test functionality in the iPad version, etc.
I found what seems a memory bug.

facts:
1. The editor memory meter shows very low consumption on my Lemur templates, which in the original Lemur hw and editor would take nearly the entire memory, but here it only shows between 13 and 15% ---that would be GREAT news if it wasn't because...>
2. The Lemur editor AND the iPad WILL delete objects ON THEIR OWN with no warning whatsoever... I mean what the total ****!!!!
3. This seems to happen when the memory is fully consumed, BUT with the fucking meter not showing more than 15%, when will I know I am reaching the memory limits?

So, questions:

1. Compared to the original Lemur, which has 4mb, what is the memory limit in the iPad version?
2. Why in hell the Lemur editor or the iPad won't warn shyte before deleting objects and entire and partial interfaces (pages) on their OWN!!!!??

Reproduce steps:

1. Create a template and put your mom there too if you can; that is put everything you have and try to consume as much memory as you can. BUT try to divide the contents into several interfaces (internal pages) within the template (name them "1", "2", etc. so you keep track of them).
2. As you keep adding stuff, everything seems fine, and the meter shows you "paradise", ie, the consumed memory is apparently very low.
3. When you reach 16%-20%, save your project somewhere.
4. Close the Lemur and open the project to see whether the whole thing is there.
5. When I do that here, the last interfaces (in alphabetical order) simply disappear on their own, and the very last one might show only some of the objects (that is, the project is AUTOMATICALLY TRUNCATED ****!!)

18 percent used, I added an excess of modules and objects, will close the project and reopen it

memory meter 18 PERCENT.JPG (43.19 KiB) Viewed 4828 times

Now when the project is reloaded into the editor, it is TRUCATED by the fucking editor with no warning, see the memory consumption of the SAME file as before!!!

new used memory when the project is opened again.JPG (16.34 KiB) Viewed 4828 times

I lost 48 hours or non-stop work due to this fucking bug. OMFG


Other than that, the porting is exceptional, good job by Axel and Liine.
Hope you guys can sort this one out. I mean, guessing when to stop adding objects to your template is too much to ask, honestly.
Also, if could reinstate the keyboard/mouse functions, that would be great. Not sure why you removed them, that was very bad news here.

I am pissed at my lost work, but I am happy because of the obvious effort you put in the porting.
Must have been a titanic project.
I have supported the Lemur project for a long time.
I own 3 original Lemurs and now the iPad version.

lmk guys please.




.

[larbatron]

I had the same problem ..... wasted days ......

[Tao-Nhan]

I can confirm the issue on my end.
Note however that this also happened with the original Jazzmutant Lemur editor, both PC and Mac versions.
Of course, now with the iPad that has bigger memory, users will definitely want to use more pages than with the original JM Lemur. I am looking forward to see a bugfix.
TN

[analog604]

Yes I can confirm the bug seems to happen in OS X and Windows versions of editor.

I wish I had read this post before yesterday when I was going nuts trying to figure out what
happened to my vars/functions that were working.

Seems the editor saves the file and truncates around 524K.

But while in memory, everything seems fine. Prob is when you load your work back into the editor from that broken .jzml

It doesn't even write the end XML tags.
My global variables and functions were the first to be chopped because they are always at the end of the file.

If you're not sure if you have hit the limit load the .jzml in a text editor (or tail in un*x). If there is no end tag of </JZML>
then it is broken.

save your work as new filenames and check them. I lost limited amount of time.. 2 hours only because i save and had exported interface sets as libraries. but THEN lost 4 hours trying to figure this insanity out and writing perl scripts to recreate some of the variables and containers lost for future time savings.


I'm having too much fun writing new code for Lemur iPad, so please please fix this save bug guys!

cheeers~
J

[djnferna]

have they fixed this yet????

[axel_liine]

We have raised the file size limit in an update, which is pending approval by Apple. Hopefully it should be out pretty soon.

[Macciza]

Isn't this the LiveControl Support section ?
I have never really looked here for Lemur discussions and do not wish to start now . . .
It would be great if people could keep it neat and post in the main Lemur discussion instead.
This would have been answered far earlier if you had

Cheers
MM

PS Seriously, the original issue is not really a 'HUGE memory bug' - it's a file-saving issue . . .

PPS This topic was originally in LiveControl Support forum - thats why my comments might seem weird . . .

PPPS It would be good if the HUGE could be removed from the title imho . . . Don't want to scare anyone off with bad information. . .

[highmountain]

When you lose all your work without warning, it qualifies as "huge."

[benj3737]

It's a huge issue to me too. I can't believe they let this bug through. Such a waste of time.

[Phil999]

although I also fell victim to this memory limitation (many hours of work lost), I wouldn't call it a bug or huge bug. It is what it is, a memory limitation.