Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4027 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

This is a script that launches a modal picker window. The last script step inserts the cursor into a field for typing. As you can see I have tried 3 methods for inserting the cursor.

 

After a variable number of uses FileMaker crashes. It crashes with any of the 3 script steps that insert the cursor in the field.

 

When the script is run from the debugger the cursor inserts properly and FileMaker does not crash.

 

When the last script step is disabled it does not crash but you now have to click into the field for typing.

 

I am at a loss as to how to get this to work. An image of the script is attached.

 

I'm working in FMPA 12.0v2 on Windows 8.

 

post-95398-0-60744300-1384239429_thumb.j

 

Further testing shows the crash is not caused by that script step. Removing the script step in question increases the number of iterations before the crash occurs so it appears it is contributing but is not the primary cause. The problem behaves exactly like a memory leak but I have no way to follow system memories and see what's going on. Any advice on debugging this script would be appreciated.

Edited by qube99
Posted

You should update to FM 12.04 - 12.02 is ancient and had many bugs.

 

Then try again.

Posted

I upgraded to 12.0v4 and that seems to have solved the problem. I've run a rather large number of iterations with no problems.

 

Thanks!

Posted

I tested this script again today and it crashed after 50-60 iterations. Disabling the insert cursor script step eliminates the crash up to > 100 iterations (I haven't tested beyond 100). Upgrading to v4 sure slowed the leak down a lot but did not eliminate it.

 

The client does not envision ever going past 10 iterations so we decided to live with it and move on. We'd rather insert the cursor and crash after 50 iterations than have to click that field each time.

 

We ran into a memory leak like this one in a C++ application that could not be cured even by CodeWarrior engineers. We hacked it by manually clearing the memories each loop which slowed us down a lot.

 

Maybe FM could fix this bug in a similar fashion.

 

Should I submit a bug report?

This topic is 4027 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.