LiveCode Forums.

Hello,

I have two medium size projects I developed in Windows 7. They are working nice - also as standalone. Now the task is to publish a Mac version as well. I have a new MacBook with OSX Mountain Lion. When opening the projects there, first the main stack shows for a second, then it says "Live Code quit unexpectedly" and crashes. Problem details tell me

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
*** CFRelease() called with NULL ***

among other stuff.

This has happened with both of my bigger projects. I tried it on another Mac (also Mountain Lion) - same problem there. One very old version of one of my projects could be opened, though. But that's not really what I need.

Does anybody have an idea how this problem could be solved?

Thanks in advance!

Kroka

Hi Kroka,

yo, irgendwas is' immer
OK, I never had these problems in the last 13 years, so lets see if we can work it out.

Try his at first in the message box:
lock messages
## supress openstack etc. handler!
go stack "/Path/to your/problemstack.livecode"

And see if it opens.
If that does not work, I can offer to take a look at your stack(s).


Best

Klaus

Hi Klaus,

thank you for your hints. Tried all that - but no luck. No way to open the stacks on Mac. Couldn't find out which element or procedure makes Livecode crash, I changed around stuff in Windows, opened on Mac again... - it always appears for a short second, then Livecode says goodbye...

But encouraging to hear that you never had any problems like this. Are you using Mountain Lion as well? I'm suspecting that the problem has to do with it. Unfortunately I have no older MacOS available to check it there.

If you'd really like to have a quick look at the stack, I'd appreciate the offer.

Thanks!

Kroka

I have mountain lion, i'd be willing to look at the stack to see if I can make it crash on mine.

Also, in the ide (without your stack open) if you click the button on the toolbar to turn off messages (same thing Klaus said to do but provides visual feedback) then open your stack, does it still crash?

I usually add an "answer" after the first line, if I get it then I move the answer after the second line, etc, etc.. once it crashes before you get the answer dialog, you will have a better understanding of where the error is happening.. obviously if it crashes after the "preOpenStack" handler, there is something else going on..

kroka wrote:Are you using Mountain Lion as well?

Yes.

kroka wrote:If you'd really like to have a quick look at the stack, I'd appreciate the offer.

Sure, just send it to klaus AT major-k.de

Solved! Klaus helped me and found the solution which is rather odd:

I created a stack in Windows. The mainstack called "Editor" had the title "Übungseditor" - including a German special character. Saved in Windows the whole stack crashed on loading in Mac. When I changed the title (yes, the TITLE, not the name of the stack) to a name without special chars, the stack would open nicely on my Mac.

I could reproduce the same problem with two other stacks I had made. Saved under Windows, the stacks wouldn't open any more on the Mac if there was some special character in the mainstack's title.

Wow - thank you, Klaus! Wouldn't have tried that myself, sometimes you have to try rather unlikely things to get things fixed.

This is obviously a bug. I'll tell runrev's support about it. It's interesting!

kroka