Author Topic: WebSite / HTML editor - what do we have?  (Read 11065 times)

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1324
  • Karma: +26/-0
    • View Profile
Re: WebSite / HTML editor - what do we have?
« Reply #15 on: February 05, 2023, 04:05:57 pm »
Dave, everyone...
Hi Dariusz, since everyone else is running it fine and it only fails for you when Firefox is open and you're using LIBPATHSTRICT, it seems the most likely is resource starvation, and memory makes sense.
...

Yup!

Messing around with VIRTUALADDRESSLIMIT (by making it larger) gets me a working Kompozer install here. Granted, this is only a half-win at best because whatever amount I increase that setting by is certainly taking away from the fs cache, and I'm sure not going to give up my giant JFS cache...LOL!

Anyways...I have my answer though.

So I'm curious: is no one else running this with LIBPATHSTRICT setting like I am?  :o

Heck, maybe the simplest solution yet - which I haven't actually tried given that the DLLs between Kompozer and our current FF would be so different - would be to drop all the provided DLLs and try to use the FF ones?

OK..another test, here we go...  8)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4805
  • Karma: +99/-1
    • View Profile
Re: WebSite / HTML editor - what do we have?
« Reply #16 on: February 05, 2023, 05:26:57 pm »
Hi Dariusz, it is not going to work using the recent FF DLL's. If you want to keep your cache, then I guess the only choice is to only run FF or Kompozer.
I'm using run!, which does the same thing as LIBPATHSTRICT. I'll attach it, drop it into your Kompozer program directory. It'll also log stdout/stderr.