Yes, we are seeing something new (since 8.0.5) on a Mac OS ( which we
cannot pin down. About half the crashes are supposedly in webstar
but there is always a corrupted heap in Frontier. And a few days ago
we had the first serious corruption in a production root in 5 years.
(We do a save copy on every root every week.) We suspect that an end
user somewhere is the trigger but that's not a useful clue on a busy
server.

Waste of time reporting kernel bugs to userland now, there's no
kernel qualified person left. Well perhaps not a waste of time, it
can be queued ready for action when the accumulated cruft of bugs
gets too big even for Userland to ignore.

I've sent 2 security alert notices to userland in the last few weeks
- I've never done that before. The first was sent to the prescribed
security@userland.com address and wasn't even acknowledged. The
second I posted on the server list but again nothing happened.

$899/year doesn't buy much these days.


>Hi.
>
>Does anyone observe regular crashes with the Frontier 8.0.5 application?
>
>It seems to be a very nasty problem - occurring not regularily and
>not everywhere.
>
>As of now it seems to be OS independent and probably is related to
>the individual consistency/structure of one or more .root files. It
>could cause crashes in a nightly task. I think Sam DeVore observed
>this in context of xml.compile/xml.decompile activity.
>
>The problem is, that the "Keep Frontier running" utility does not
>work on NT, because the Dr. Watson dialog prohibits the restart.
>
>I mailed frontier-bugs@userland.com, but as usual didn't get any
>reply on this.
>
>Regards,
>Oliver
>
>--


--

- David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.

Enclosures

None.  

Replies