Sign in to follow this  
Followers 0

FM 12 Advanced 03 BUG... or is it?

40 posts in this topic

Posted

I'm unclear what you are asking, "Does FMI know about this bug?" I thought I saw your posting over on FileMaker Report An Issue. And on post #18 you said you reported it to FMI. That is the only place in the universe where we might hear confirmation from FMI although the quality of their response is usually anti-climactic. That forum is where you can read about bugs and report them. If you do not get confirmation after you post, you can bug them by posting on the thread again.

Am I misunderstanding your question? :-)

0

Share this post


Link to post
Share on other sites

Posted

Question: " Does FM know about this bug? Should I post it in response to this posting? (I know the forum doesn't like multiple postings on the same thing

I'm confused by your post. :(

You stated in an earlier post (#18) that you HAD reported it (Although I don't know why we had to ask you so many times before you admitted it.) :(

Please do not start another topic about this, just keep it here.

The FMForums is not part of FileMaker Inc, and any communication you want them to have, needs to be sent to them direct.

As a side note, I don't know of any one at FileMaker Inc, that even reads the FMForums.

Lee

0

Share this post


Link to post
Share on other sites

Posted

I'm confused by your post. :sad:

You stated in an earlier post (#18) that you HAD reported it (Although I don't know why we had to ask you so many times before you admitted it.) :sad:

Please do not start another topic about this, just keep it here.

The FMForums is not part of FileMaker Inc, and any communication you want them to have, needs to be sent to them direct.

As a side note, I don't know of any one at FileMaker Inc, that even reads the FMForums.

Lee

Lee,

Your confusion probably centers around different interpretations of what "report it to them..." means. Since I am not in regular contact with FM and since you did not define what "report it to them" looks like, the definition of what the 'behavior' of reporting is left to my definition.

To me it looks like I went into the FM forums and created the question and resulting thread. What does the behavior of reporting look like to you? :logik:

0

Share this post


Link to post
Share on other sites

Posted

Ahm, I supplied the link in 12 but I realize I also said I would try to test but I couldn't - I was away from computers and only tested quickly on one windows box. And someone posted about it over on FileMaker Forums Report An Issue. Regardless, you are communicating and that helps everyone who searches for same issues. But FMI needs to be told. As Lee says, FM Forums (and all the other forums) aren't FMI. :)

Anyway if you haven't posted on that thread I provided in Post #12 then please do so. :yep:

0

Share this post


Link to post
Share on other sites

Posted

Thanks LaRetta. Very useful information.

Just to be sure, I went to the link and 'reported' the problem. By way of me 'not forgetting', below is the report.... :laugh2:

post-72145-0-48405900-1351808063_thumb.j

0

Share this post


Link to post
Share on other sites

Posted

November 10.  Update.

 

I've heard nothing from Filemaker.  It will be interesting to see if they come out with v 4?

0

Share this post


Link to post
Share on other sites

Posted

Hi Ron, :smile:

 

I am keeping my fingers crossed.  With the issues being reported, I can't imagine NOT coming out with v4.  But then ... that is what I thought about 10 and 11 (Windows) as well. :hmm:

0

Share this post


Link to post
Share on other sites

Posted

Just a quick update.

 

I downloaded upgrade v 2 and it too creates the 'Filemaker Crash' situation as does v 3.

 

V1 DOES NOT create this problem. 

0

Share this post


Link to post
Share on other sites

Posted

I think I got it working in v 3!!!!

 

I had a much more complicated application that worked as expected.  Other people have not registered the same complaint (that I know of).  So, the error must be in my app somewhere.  But, the script that causes the error runs without error in debug?!  So, opened the menu script and copied it to the clipboard.  Then I created a 'new' script and pasted that code into it.  I reassigned the script trigger to the new script and it works.   

 

Does this mean that I / FM created a corrupted script?  Has anyone heard of that?

0

Share this post


Link to post
Share on other sites

Posted

Correction.  It worked when I made the popup selection about 50 times.   Just a few minutes ago it blew up again!  I just tried this app on a Windows 7 machine and it worked perfectly. (so far)

 

  If so, this situation begs the question "Is it OSX 10.8.2 ?  Is FM 'rated' to run with 10.8.2?

 

Here is a YouTube video of the crash:  http://youtu.be/e4YuKfL6CcU

 

Back to v 1 

 

======================

 

Here is the latest error readout:

Process:         FileMaker Pro [81585]
Path:            /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
Identifier:      com.filemaker.client.advanced12
Version:         12.0.3 (12.0.3)
Code Type:       X86 (Native)
Parent Process:  launchd [174]
User ID:         501

Date/Time:       2012-11-17 01:20:26.938 -0800
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version:  10

Interval Since Last Report:          171198 sec
Crashes Since Last Report:           6
Per-App Interval Since Last Report:  8664 sec
Per-App Crashes Since Last Report:   4
Anonymous UUID:                      A9C064AE-41AE-F9A9-2AF2-299B873AE405

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000038820207


VM Regions Near 0x38820207:
    __LINKEDIT             0000000038313000-000000003842b000 [ 1120K] r--/rwx SM=COW  /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/Frameworks/libxalan-c.dylib
-->
    __TEXT                 0000000040000000-0000000040006000 [   24K] r-x/rwx SM=COW  /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/Frameworks/libxalanMsg.dylib

Application Specific Information:
Java information:
 Exception type: Bus Error (0xa) at pc=000000000411ca49
 
 Java VM: Java HotSpot Client VM (20.12-b01-434 mixed mode macosx-x86)
 
Current thread (000000001a1ea000):  JavaThread "Thread-1" daemon [_thread_in_native, id=-1396413912, stack(00000000bf800000,00000000c0000000)]
Stack: [00000000bf800000,00000000c0000000]
 

0

Share this post


Link to post
Share on other sites

Posted

Latet update:  NOV 17

The field the popup was based on is a 'global' field named MenuReport in the Global table. 

 

I created a global field in Patient name MenuReport and selected that as the popup source.

So far... everything works.  Why?

 

Shouldn't Global::MenuReport work just as well as Patient::MenuReport??

 

ron

0

Share this post


Link to post
Share on other sites

Posted

Nov 24, 2012

Update:  After working on 2 different apps, I returned to working on the Medical Records app that caused the problem.  After producing a runtime version, I shut down FM and tried the created app.   After only 2 selections ... it shut down Filemaker!!! 

 

So, it is back to 12 v 01.... Since 02 and 03 both blow up FM.  Strange that FM is not interested in this.... Oh well.

0

Share this post


Link to post
Share on other sites

Posted

I don't get it. When a runtime app is running, FileMaker isn't, no? You do say you exited (quit?) filemaker then ran the runtime. Are you saying your runtime crashed?

0

Share this post


Link to post
Share on other sites

Posted

I don't get it. When a runtime app is running, FileMaker isn't, no? You do say you exited (quit?) filemaker then ran the runtime. Are you saying your runtime crashed?

Right.  From FM I created the RT.  I then shut down FM and ran the .app.  It crashed just like when I run the application from within FM.

 

Here is another update:

Each 'choice' in the popup (see the movie in the previous posting) became a application MENU choice.  The menu ran the same code that created a window and loaded a layout.  I then upgraded from v1 to v3 and, from FM, ran my FMP12 file.  I made menu 25 choices and it did NOT CRASH.   If this holds, it would mean that FM has an issue with their POPUP control.  (fingers crossed)

0

Share this post


Link to post
Share on other sites

Posted

DEc 26, 2013

Here is the latest.

This issue has been absent since I last reported on it.  I have created several apps and work on a daily basis in FM 12 Adv 04.  Not a problem.

 

Then just a few days ago, while on my Windows 7 PC, FM started crashing again.  So, I copied the file to my OSX machine and it too crashes.

 

The app is really simple.  Does anyone want to try it on their machine to see if it will crash for them?

 

Let me know and I will upload the fmp12 file.

 

Ron

0

Share this post


Link to post
Share on other sites

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
Sign in to follow this  
Followers 0