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

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

Recommended Posts

  • Newbies
Posted

I have to keep restartung Instant web publishing or change the log idle users off time in order to restart the web service. The database itself is accessible through Filemaker. This is my console log...does anyone know what it means? The only thing I know is that it's referring to the Filemaker app process and not the IWP process because of the ID number. Thanks.

------------------------

Mac OS X Version 10.3.5 (Build 7M34)

2004-08-13 09:29:19 -0400

*** malloc_zone_malloc[352]: argument too large: 4294967295

*** malloc[352]:) Deallocation of a pointer not malloced: 0xbfffef80; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug

Posted

malloc is generally known in programming to allocate memory for pointers. it can be a hardware problem too, though.

free() is to free the memory that's allocated for pointer or other variable types.

sometimes the log doesn't necessary point to the problem itself... i think you still need to investigate yourself what the problem is.

  • 2 weeks later...
Posted

I am running FMP7 IWP on a Windows 2003 Server, and I regularly encounter a similar problem. After being left unattended for a random amount of time (a day or two), "FM Web Publishing.exe" crashes. It does not produce a UI error, nor does it register in the system Event Log. The best clue I can find from any log is an error "200" in the web "application.log"

I have to turn "Instant Web Publishing" off and then on again (or reboot filemaker entirely) in order to restart FM Web Publishing.

Any clues as to what may be causing this or how to fix it would be greatly appreciated.

  • Newbies
Posted

I tried everything and the last thing I tried worked. It appears at least with OS X that FMP7 IWP does not like port 80. All I did was changed the port to 8080 and it's been up and running ever since. This might also work on Windows. FMP v.6 did not have this problem.

::M::

This topic is 7395 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.