"MoSync Panic 40028" while debugging the "MoSync MAUI Project" template (MoSync 2.6, Windows 7)

5 posts / 0 new
Last post
babicch
babicch's picture
Offline
Joined: 14 Sep 2011
Posts:
"MoSync Panic 40028" while debugging the "MoSync MAUI Project" template (MoSync 2.6, Windows 7)

Hello,

I tried to debug a new created "MoSync MAUI Project" directly out of the "MoSync Project Template". After starting the MoSync/Emulator, a "MoSync Panic 40028" pops up and tells something about "Memory alignment error" "The panic occurred in the MoSync core."

Well, I play around with some project settings and finally reduced the values of the "Memory Settings" from originally H: 512, S: 128, D: 1024 to H: 128, S: 64, D: 256. With these settings the project debugs perfectly…

But I’m just wondering why? Reducing the available memory normally isn’t the way running an application better…

Best regards,
Christian

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Sam Pickard
rival's picture
Offline
Mobile Archmage
Joined: 19 Mar 2009
Posts:

Hi, have a look here - http://www.mosync.com/blog/2010/11/quick-note-memory-alignment-errors

Have you created any new objects in the template? Changing the memory settings will change what gets overwritten in memory, or referenced incorrectly, which is why its working when you reduce the memory.

babicch
babicch's picture
Offline
Joined: 14 Sep 2011
Posts:

Hi!

No, I didn’t modify the template. Actually I just want to debug the destructor of "MAUIScreen", because I think its implementation is wrong. "delete mTouchArea;" shouldn’t work, because "mTouchArea" it is already deleted by the destructor of "mBackgroundArea". ("mTouchArea" ist a child widget of "mBackgroundArea")

Sam Pickard
rival's picture
Offline
Mobile Archmage
Joined: 19 Mar 2009
Posts:

Ah, deleting an object which is already deleted could easily cause a memory alignment error - I'll have a look

Sam Pickard
rival's picture
Offline
Mobile Archmage
Joined: 19 Mar 2009
Posts:

You're not wrong. Another user has reported this. It appears to be a bug with the MAUI::Label code. I've raised an issue here: https://github.com/MoSync/MoSync.