to Mesa. The current solution is based on a diff from jsg@.
Also fix font redering issues with WebKit, with 3rd party TTFs with a
diff from Yoshihisa Matsushita.
if the SingletonLock file is available and valid.
The problem is that when chrome crashes one of the destructors fail to
remove the lockfile and then when you start chrome again, it will
try to communicate with the old PID of the chromium main process, because
the SingletonLock file will point to `hostname`-PID_of_old_chromium and
since that process is not running anymore, startup will fail.
- skip the tests if you already have a running chrome instance
- default to 'no' (meaning you must not use the mouse for doing the
sensible thing)
- do not start chrome if you just close the window (alt+f4 etc)
ok robert@
this makes chrome use way less memory and since it does not hit
datasize limits anymore, it is way more stable too
- remove the warning of datasize bumping from the wrapper script
tested by sthen@, jasper@ and me
(you may still need to raise them if you open many tabs, but this
should be enough to avoid problems in normal use), only warn if
softlimits can't be raised, and adjust messages to mention login.conf
(and login.conf.db if detected).
ok espie@ "feel free to modify it if you don't like it" robert@
time right now.
Tree is still locked!
Reasons for the update:
- good work that can be used now
- only builds on i386/amd64, and they're fast
- multiple security problems in old chrome
- old chrome half working, can't break it more than it was.
This one requires resources (see MESSAGE), but it's ways more stable.
Again, discussed with sthen@, jasper@, naddy@, miod@
i386 and amd64 supported.
Chromium is an open-source browser project that aims
to build a safer, faster, and more stable way for all
Internet users to experience the web. http://www.chromium.org/
This is version 4.0.251.0 with a tarball already including hundreds
of patches by myself, Sprewell, Ben Laurie and others from the original
FreeBSD effort. See homepage for more details and known issue:
http://sightly.net/peter/openbsd/chromium/
(right now, there are i386 & amd64 -current packages there that can
be pkg_add'ed, links to the FreeBSD page for more info, etc)
The patches are being cleaned up and sent upstream in chunks, the
goal will be to have a clean tarball eventually. I _just_ got this
working earlier this week so it may crash and burn (especially on
amd64 as some parts do not appear 64-bit clean), let me know.
"commit it and let's work on it in-tree" espie@, robert@ & others
