[chromium-dev] OS X IPC Design doc

Hi, You can find the design document for OS X IPC at: http://sites.google.com/a/chromium.org/dev/developers/design-documents/os-x-interprocess-communication This document is a work in progress, feedback and comments are welcome. Best regards, Jeremy --~--~-~--~~~---~

[chromium-dev] Re: OS X IPC Design doc

I think the decision is pretty clear for us. I definitely agree with you about the performance tests - if we don't have those already, it would definitely be good to add a bunch of them for the IPC Channel. Best regards, Jeremy On Wed, Nov 5, 2008 at 1:37 PM, Jeremy Moskovich <[EMAIL PRO

[chromium-dev] Re: OS X IPC Design doc

have a > shared implementation that meets all of our requirements. > > What are the requirements? > > -Darin > > > On Wed, Nov 5, 2008 at 2:05 PM, Jeremy Moskovich <[EMAIL PROTECTED]>wrote: > >> Replying to a previous comment by jam: >> >>> I

[chromium-dev] Re: OS X IPC Design doc

mmand line. Best regards, Jeremy On Wed, Nov 5, 2008 at 1:37 PM, Jeremy Moskovich <[EMAIL PROTECTED]>wrote: > > Hi, > > You can find the design document for OS X IPC at: > > http://sites.google.com/a/chromium.org/dev/developers/design-documen

[chromium-dev] Re: Fwd: [chromium-dev] Re: OS X IPC Design doc

We ran some benchmarks of Mach ports vs FIFOs on OSX, you can find the results in the "Performance Considerations" section of the Design doc . Best regards, Jeremy > --~--~-~--~~--

[chromium-dev] Re: Fwd: [chromium-dev] Re: OS X IPC Design doc

[EMAIL PROTECTED]> wrote: > > On Wed, Nov 12, 2008 at 4:46 PM, Jeremy Moskovich <[EMAIL PROTECTED]> > wrote: > > We ran some benchmarks of Mach ports vs FIFOs on OSX, you can find the > > results in the "Performance Considerations" section of the Design do

[chromium-dev] Starting work on pipe-based IPC implementation

Hi, I'm starting work on a pipe-based implementation of the IPC::Channel, I just wanted to make sure no-one else was working on this in parallel. There are still some open questions regarding how Mach messages mesh with libevent so until we have all the information on that, it would be good to ha

[chromium-dev] Re: common/ipc_* and renderer

Sent from wrong address, resending... I'm untangling the IPC::Channel code at the moment, as part of that effort > I'll remove or replace the MessageLoopForIO::IOHandler stuff. > > Best regards, > Jeremy > > > On Wed, Nov 26, 2008 at 10:47 AM, Mike Pinkerton <[EMAIL PROTECTED]>wrote: > >> >> Just

[chromium-dev] Linux/OS X IPC + Updated design doc.

The Linux/OS X IPC code is now in the tree. I still need to fix a few things and land a refactoring for message_pump_libevent but by and large whats in there should be useable. Having said that, my intent going forward is to continue bringing up surrounding infrastructure, so if you plan on touch

[chromium-dev] Re: Linux/OS X IPC + Updated design doc.

Mach ports. It turns out that we had the same performance problem on > Windows when I tried converting IPC::Channel over to using > base::ObjectWatcher (i.e., RegisterWaitForSingleObject) due to the thread > context switching overhead. > -Darin > > > > On Fri, Dec 12, 2008

[chromium-dev] Re: Getting started, getting blocked...

Personally I've never seen that error before. I'd suggest you try checking out a fresh copy. Let us know if that fixes things... Best regards, Jeremy On Thu, Dec 18, 2008 at 12:34 PM, Jaff wrote: > > Hi, > > I've been wanting to get into some contribution-mode, so I have gotten > far enough t

[chromium-dev] Fwd: Flakiness in net_unittests on Mac Debug

Whoops, forgot to cc chromium-dev, also see the reply from dkegel... -- Forwarded message -- So the CHECK() failing means that MessagePumpLibevent::Init() is returning false. This could be the result of failures in: * Creating the pipe() (line 84) * Setting either end to Non-bloc

[chromium-dev] Fwd: Flakiness in net_unittests on Mac Debug

we should just check in the attached patch so we can learn more next time it happens. On Tue, Dec 23, 2008 at 10:40 AM, Jeremy Moskovich wrote: > Too many open FDs causing pipe() to fail? > > Are any of you able to repro this locally? > > Best regards, > Jeremy > > On Tue,

[chromium-dev] [chromium-reviews] Re: Started to try to fix issue 3661

Hi, Feel free to send me the review. The important part is to assign the review to someone knowledgeable in the respective area of the code, all the people Dean listed would be a good match in this case. In general, if you have any doubts about who to send a review to, you can ask on irc, on chr

[chromium-dev] Sending FDs between processes in the face of the OS X Sandbox.

There's been discussion recently about sending FDs between processes so that renderer processes can access files directly. I ran some tests on OS X to see whether you can send an FD when the receiving process is sandboxed. It turns out that this does indeed work, even when using the more restrict

[chromium-dev] Debugging the renderer process on OS X

Just a quick note, since this may be generally useful: If you pass the --renderer-startup-dialog when running the browser (or the unit tests) then any spawned render process will print a message to stdout with it's pid and then call pause(). XCode doesn't like debugging multiple processes, so wha

[chromium-dev] Re: Debugging the renderer process on OS X

FYI, this just describes how things are hacked up to work at the moment for the benefit of people trying to bring stuff up. I assume that there are better ways to do this in the long run. Best regards, Jeremy On Thu, Feb 5, 2009 at 4:57 PM, Jeremy Moskovich wrote: > Just a quick note, si

[chromium-dev] Re: Debugging the renderer process on OS X

OK, I've added this and some other useful info to the dev wiki at: http://sites.google.com/a/chromium.org/dev/developers/debugging-on-os-x jam,maruel: Thanks for the info! Best regards, Jeremy On Thu, Feb 5, 2009 at 5:12 PM, Jeremy Moskovich wrote: > FYI, this just describes how th

[chromium-dev] Re: Claimings

I'm tightening up the IPC Channel tests and adding some Mac-specific ones... > On Mon, Feb 9, 2009 at 3:37 PM, John Grabowski wrote: > >> (We talked about a spreadsheet for this... anyone have a link?) >> I'm following the chain from " on URL in browser" --> "tell renderer >> do something". Thi

[chromium-dev] Re: [POSIX] Debugging renderers

Nice! :) Could you add a note about this to this to the wiki? Best regards, Jeremy On Mon, Feb 9, 2009 at 5:19 PM, Adam Langley wrote: > > Now that both Mac and Linux are spawning renderers, I added a command > line flag: --renderer-cmd-prefix. This lets one prefix the renderer > command line.

[chromium-dev] Re: Mac Dogfood Planning

I'll tackle breakpad support, if anyone else is already working on this, please ping me. Best regards, Jeremy On Mon, Mar 2, 2009 at 9:27 PM, Mike Pinkerton wrote: > > As we're making rapid progress, I wanted to start to organize a little > more around the "5 minute browser" goal for the end of t

[chromium-dev] focusRingColor() listening to system settings changes on Windows?

(mailed to random people who I thought might know the answer). In platform/graphics/chromium/ColorChromium.cpp we currently hardcode the value of focusRingColor on OS X & Windows. On OS X Safari listens on a notification to see if the user has changed the system focus color. Is there a similar no

[chromium-dev] Layout test regressions in latest merge

The last couple of merges have brought with them a considerable number of new layout test failures. I've filed http://crbug.com/9581, http://crbug.com/9582, http://crbug.com/9595 and http://crbug.com/9578 to track the new failures. If you have some spare cycles I'd very much appreciate your help f

[chromium-dev] Re: sizes in the perf dashboard

+1 It's great that we can track this info now, thanks for doing this! Nicolas: Could you possibly add the contents of your email to the wiki? sgk: How about adding links from the top of the page to the size graphs? Since they're way down at the bottom of the page it's easy to miss them. It would

[chromium-dev] Re: Today we run zero LayoutTests in chrome

+1 That would be extremely useful to the Mac port as well. WebKit calls a bunch of OS X APIs that are not specced in regards to their interaction with the Sandbox (i.e. they may try to open arbitrary files, talk to the network, etc and fail in the process). We have no good source of test coverage

[chromium-dev] Some help with Layout Test regressions

Hi, Today's WebKit merge (42932:42994 - http://trac.webkit.org/changeset?new=42...@trunk&old=42...@trunk) has brought in some new regressions. If anyone has any spare cycles I'd really appreciate it if you might be able to look at these - http://crbug.com/11178: xss stuff: LayoutTests/http/tests/

[chromium-dev] Re: Unforking: Canary Bot Lives!

+100!! Awesome!!! On Fri, May 1, 2009 at 2:42 PM, Scott Hess wrote: > > HEROIC! > > On Fri, May 1, 2009 at 2:38 PM, Dimitri Glazkov > wrote: > > > > Hello all, > > > > This is kind of a momentous occasion. For the first time -- ever, our > > WebKit Canary bot (the one that pulls directly from W

[chromium-dev] Help: WebKit builder out of diskspace

Can anyone resolve this so we can reopen the tree? Thanks, Jeremy --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~-

[chromium-dev] Re: Renderers "Not Responding"

I just pinged Avi about us, my guess is that the Sandbox is blocking connections ot the Window Server. Adding (debug deny) to the sandbox spec file will print messages to console when things like this happen, I'll add a note about that to the Wiki ( http://dev.chromium.org/developers/debugging-on-o

[chromium-dev] Re: Renderers "Not Responding"

, Jeremy On Fri, May 22, 2009 at 11:36 AM, Mike Pinkerton wrote: > Does the problem go away if we disable the sandbox? > > On Fri, May 22, 2009 at 2:02 PM, Jeremy Moskovich > wrote: > > I just pinged Avi about us, my guess is that the Sandbox is blocking > > connecti

[chromium-dev] Re: Which is the Xcode project for chromium on MacOS

The XCode projects are generated from the .gyp files in the source tree. If you follow the instructions on the wiki, you should get a buildable tree: http://code.google.com/p/chromium/wiki/MacBuildInstructions Best regards, Jeremy On Tue, May 26, 2009 at 10:37 AM, Daniel Dreiberg < daniel.dreiber

[chromium-dev] Re: chrome://downloads/ behaviour (some suggestions and a bug, i think)

>From what I understand from your email, you're asking for consensus about the following aspects of download progress, please correct me if I'm wrong or if there are additional issues: * DL speed isn't reported for items of a known size (regression) - [yoav: is there a bug open for this?] * Change

[chromium-dev] Fixing our keyboard handling act on OSX

Hi All, We currently fudge our keyboard handling on OSX, we interpret command key shortcuts ourselves and thus miss out on quite a few Cocoa text handling niceities. We also don't support IMEs. Relevant bugs: http://crbug.com/10862 - OS X: Can't use command-key shortcuts with foreign keyboard lay

[chromium-dev] Re: Fixing our keyboard handling act on OSX

@chromium.org > > On Thu, May 28, 2009 at 7:14 AM, Jeremy Moskovich > wrote: > > Hi All, > > We currently fudge our keyboard handling on OSX, we interpret command key > > shortcuts ourselves and thus miss out on quite a few Cocoa text handling > > niceities. We a

[chromium-dev] Re: making UI tests pass in RTL (question)

xji or idana will correct me if I'm wrong here. But I think what you want is: l10n_util::GetTextDirection() == l10n_util::RIGHT_TO_LEFT Best regards, Jeremy On Thu, May 28, 2009 at 1:56 AM, nakro wrote: > > Hi all, i am right now trying to make the UI_Tests to pass on hebrew > enabled windows

[chromium-dev] Re: making UI tests pass in RTL (question)

Or perhaps View::UILayoutIsRightToLeft() would be a better fit. On Thu, May 28, 2009 at 12:16 PM, Jeremy Moskovich wrote: > xji or idana will correct me if I'm wrong here. > But I think what you want is: > > l10n_util::GetTextDirection() == l10n_util::RIGHT_TO_LEFT > >

[chromium-dev] Re: Fixing our keyboard handling act on OSX

start working on this pretty soon. Evan: I'll cc you on all relevant code reviews, that way we'll hopefully be able to create some good cross-platform plumbing for this stuff. Best regards, Jeremy On Thu, May 28, 2009 at 2:58 PM, Evan Martin wrote: > On Wed, May 27, 2009 at 3:

[chromium-dev] Re: How to debug Chrome on MacOS

Looks like you're hitting a DCHECK() in the code, I'm guessing it has to do with a corrupt profile. Try deleting your profile. There's a wiki page with some tips on debugging the OSX version here: http://dev.chromium.org/developers/debugging-on-os-x Best regards, Jeremy On Thu, May 28, 2009 at

[chromium-dev] Re: a brave new world for RTL languages (please comment)

Hi Yoav, In general it would be much easier to have a discussion if you could refer to a specific narrowly-focused bug in your email. Just saying that an area is generally broken it's hard to understand what specific aspect you're talking about. So: What exact functionality is broken, and how do

[chromium-dev] Re: a brave new world for RTL languages (please comment)

There are quite a few thorny corner cases around BiDi editing and cursor movement, I don't think there's any point in having a discussion about this stuff unless we have a handle on what we want to fix and exactly how we plan to fix it. Also, IMHO, it would be better to iron out some of the basic

[chromium-dev] Please ping me if you plan on touching the OSX keyboard handling code

We have a bunch of bugs around keyboard handling on OSX since we currently bypass the Cocoa event handling system. I've started to look into some of these issues. Please touch bases with me if you plan on touching the event code on OSX. Duplicating work really sucks. Thanks, Jeremy --~--~--

[chromium-dev] Re: a brave new world for RTL languages (please comment)

If you post a link to a bug that describes a single, concrete, narrowly defined issue along with a proposed solution we can discuss that. I understand you see allot of stuff you want to fix, which is great. But if you continue to post messages that contain a bunch of different issues mixed togeth

[chromium-dev] Re: Please ping me if you plan on touching the OSX keyboard handling code

it becomes OK, I'm going to notice you. > > Regards, > > Hironori Bono > E-mail: hb...@chromium.org > > 2009/6/3 Jeremy Moskovich : > > We have a bunch of bugs around keyboard handling on OSX since we > currently > > bypass the Cocoa event handling > >

[chromium-dev] Re: chrome-bisect.py: Mac Chrome Continuous Build Archive Bisecting

That's great and I don't mean to belittle the awesomeness of this in any way but: git has built-in support for this along with many other advantages over SVN, I use git along with the gitx gui on OSX and it's greatly increased my productivity. It would make me much happier if more people on the te

[chromium-dev] Re: Fixing our keyboard handling act on OSX

)? > > > > Regards, > > > > Hironori Bono > > E-mail: hb...@chromium.org > > > > On Thu, May 28, 2009 at 7:14 AM, Jeremy Moskovich > wrote: > >> Hi All, > >> We currently fudge our keyboard handling on OSX, we interpret command > key

[chromium-dev] Re: Fixing our keyboard handling act on OSX

re to work better with Cocoa? Best regards, Jeremy 2009/6/7 Jeremy Moskovich > Hi Hironori, > > Thanks for the detailed report. > > I haven't nearly the same insight into the text input system as you and Avi > do, but from what I've seen it may be possible for us to

[chromium-dev] Re: Adding Mac OS X Spellchecker to Chromium

IMHO there is no need to maintain dual hunspell/OSX spellchecker backends. There are addon OSX spellcheckers for other languages e.g. http://www.mitzpettel.com/software/hspell.php . Writing additional spelling servers is pretty simple so I think the correct approach would be: 1. Getting OSX spel

[chromium-dev] Re: Adding Mac OS X Spellchecker to Chromium

s is done in WebKit and match the behavior there as much as possible, that's what I'm doing with the keyboard events at the moment and it's proving pretty fruitful. It's really exciting you're working on this!! Best regards, Jeremy On Tue, Jun 9, 2009 at 5:50 PM, Jeremy Mosk

[chromium-dev] Re: Is there any logging to print out messaging between Browser and Renderer

You can set the environmental variable in XCode by double clicking on the executable target. I'm not sure the logging code is enabled on OSX, the right place to look would be in chrome/common/ipc_channel_posix.cc, search for IPC_MESSAGE_LOG_ENABLED. If that's compiled in, then if the env variable

[chromium-dev] Re: Changing the language of the spellchecker?

The canonical example you should be following here is WebKit on OSX. Grepping the sourcecode for NSSpellChecker shows usage in WebKit/mac/WebCoreSupport/WebEditorClient.mm and WebKit/mac/WebView/WebHTMLView.mm WebKit/mac/WebCoreSupport/WebEditorClient.mm:638,664 : NSRange range = [[NSSpellChecker

[chromium-dev] Re: How to attach to Renderer Process in XCode

You can find instructions here: http://dev.chromium.org/developers/debugging-on-os-x Ultimately, we should really combine all the platform debugging articles into one page :| Best regards, Jeremy On Thu, Jul 16, 2009 at 9:29 AM, hap497 wrote: > > Hi, > > chromium.org has this http://dev.chromi

[chromium-dev] Re: How to attach to Renderer Process in XCode

911 wrote: > On Thu, Jul 16, 2009 at 12:46 AM, Jeremy Moskovich > wrote: > > You can find instructions here: > > http://dev.chromium.org/developers/debugging-on-os-x > > Ultimately, we should really combine all the platform debugging articles > > into one page :| &g

[chromium-dev] Re: Question about chromium sandbox on Mac OSX

Hi, It would really help if you could provide some details on what your trying to do. Best regards, Jeremy On Thu, Jul 30, 2009 at 9:06 AM, n179911 wrote: > > Thank you. Can you please tell me how can I change the configure file > (renderer.sb) to use > other sandbox profile, like the one descr

[chromium-dev] Re: Question about chromium sandbox on Mac OSX

Is this just out of curiosity? Is there something specific you're trying to achieve? On Thu, Jul 30, 2009 at 9:32 AM, n179911 wrote: > On Thu, Jul 30, 2009 at 9:08 AM, Jeremy Moskovich > wrote: > > Hi, > > It would really help if you could provide some details on what

[chromium-dev] Re: Question about chromium sandbox on Mac OSX

wrote: > I would like to change it so that the renderer can create/write file on > /tmp. > > Like this 'kSBXProfileNoWriteExceptTemporary' profile. > > On Thu, Jul 30, 2009 at 9:43 AM, Jeremy Moskovich > wrote: > > Is this just out of curiosity? Is there

[chromium-dev] Re: Question about chromium sandbox on Mac OSX

wrote: > > Thank you all. I have a better understanding now. > > I just try to log some debug info of the renderer in /tmp that may > help me understand things better. > > Regards, > > On Thu, Jul 30, 2009 at 7:36 PM, Jeremy Moskovich > wrote: > > The easiest way w

[chromium-dev] Topcrash on OSX - crbug.com/17555 - Renderer dies on WTF::HastSet

This is the top crash on OSX by far as of 3.0.196.0. >From Dimitri's comment on the bug: """ It appears that somehow a message from BrowserRenderProcessHost catches the RenderProcess with its pants down, where WebView hasn't been created and the WebCore::Page constructor hasn't been called yet. "

[chromium-dev] Re: Topcrash on OSX - crbug.com/17555 - Renderer dies on WTF::HastSet

No, we don't have a repro, but what you mentioned sounds promising. Thanks, Jeremy On Fri, Jul 31, 2009 at 11:48 AM, Jeremy Orlow wrote: > On Fri, Jul 31, 2009 at 11:42 AM, Jeremy Moskovich wrote: > >> This is the top crash on OSX by far as of 3.0.196.0. >> From Dimit

[chromium-dev] DTrace/OSX links

I've collected some useful links on DTrace [esp. for OSX], some of you probably know this cold but for those who don't: jgm's awesome introductory article: http://www.mactech.com/articles/mactech/Vol.23/23.11/ExploringLeopardwithDTrace/index.html Defining static probes on OS X: http://www.macresea

[chromium-dev] Updating a git repo?

One of the nice things about git is that you can pull down a large chunk of upstream changes really fast. I have a tree checked out from git.chromium.org and the command I'm using to update is: $ git svn fetch && git svn rebase && gclient sync So basically I'm pulling down revisions one by one fro

[chromium-dev] [Linux folks] Splitting First Run into it's own process

I'm looking at splitting the First Run UI & import machinery into it's own process on OS X. I just wanted to sync up with people working on the Linux side of things to make sure no-one else is working on the same thing in Linux-land? Best regards, Jeremy --~--~-~--~~~-

[chromium-dev] Re: [Linux folks] Splitting First Run into it's own process

it's interaction with the main app runloop, There are also UI artifacts - http://crbug.com/19643 Best regards, Jeremy > > On Fri, Aug 21, 2009 at 5:11 PM, Jeremy Moskovich > wrote: > > I'm looking at splitting the First Run UI & import machinery into it's > ow

[chromium-dev] Re: Git woes

Git is comprised of billions of tiny orthogonal binaries. When this happened to me the cause was some old git binaries in the path that where being called by others, the version mismatch was silent and caused this error. Have you upgraded to a new version of git recently that might cause such a mi

[chromium-dev] OS X debugging tip - turn off the sandbox.

When the sandbox gets in the way of the kernel or other parts of the system, very strange things can happen. If you're running into unexplained behavior on OS X try disabling the sandbox by running with --no-sandbox. This was the key to a crash we where looking at today which is why I'm sending t

[chromium-dev] Re: Chromium IPC layer in 64-bit MacOS

Hi Mark, We haven't specifically tested the ipc layer as a method to communicate between 64 & 32-bit processes on OS X. At it's core the IPC layer just consists of a pipe to which we read & write binary data, therefore if the binary representation of the data types that you want to push over the i

[chromium-dev] Re: Layout try slaves

Also documented here: http://sites.google.com/a/chromium.org/dev/developers/try-server-usage Along with a list of tests currently run by the trybots. Best regards, Jeremy On Mon, Aug 31, 2009 at 1:12 PM, Marc-Antoine Ruel wrote: > > On Mon, Aug 31, 2009 at 12:39 PM, Brett Wilson wrote: > > On M

[chromium-dev] Re: Updated UsingGit wiki for WebKit developers

Major kudos for helping to improve our documentation!!! Evan [I think] actually created a script in 'tools/sync-webkit-git.py' which has support for syncing the right version of WebKit (the one gclient expects) via git into our source tree. So I think referring to that would provide better documen

[chromium-dev] Re: Where I can find the all.xcodeproj for building chromium on MacOSX

If you look at the checkout instructionslinked to from the build instructions, it says the following: """ 1. Updating your checkout once by running gclient sync --force in the source code directory. 1. If you don't want to sync,

[chromium-dev] Re: How expensive is setting a crash key for breakpad?

That sounds like a great idea!! Note that there are some limits on crash keys, here's the relevant quote from breakpad.h: """ // User defined key and value string storage. Generally this is used // to configure Breakpad's internal operation, such as whether the // crash_sender should prompt the u

[chromium-dev] Stack trace wrapping when filing bugs

crbug.com appears to wrap input to the width of it's textarea, that means that if you paste a stack trace into a bug at the default width the output is wrapped and becomes really hard to read. e.g. http://crbug.com/24172 . It would be really helpful if people dragged the little grabber on the texta

[chromium-dev] Re: Stack trace wrapping when filing bugs

16 PM, Ojan Vafai wrote: > This seems like a Google Code bug to me. Pasting stacktraces should be a > use-case Google Code cares about. Have you filed a bug with them? > Ojan > > On Fri, Oct 9, 2009 at 11:17 AM, Jeremy Moskovich wrote: > >> crbug.com appears to wrap input to the

[chromium-dev] Re: Tech talk topics

IMHO it would be immensely valuable to give a talk explaining what Layout tests are and how they work in a *simple* enough manner to allow web developers to create tests for bugs that affect them. I haven't found any easily discoverable introductory material on this topic. Best regards, Jeremy O

[chromium-dev] Re: Worker processes are now sandboxed on OS X

return false; > #endif > > > > If MacOS still defines OS_POSIX, doesn't this mean your changes further > down are not actually running? > > Also, by "worker process" did you mean "utility process"? (Do we have > something called a "worker p

Re: [chromium-dev] Re: Assertion failures on Mac OS are super slow

FYI: We have such suppression code in the tree which we use for the renderer process. For the browser process we allow the crash to reach Crash Reporter so that Chrome doesn't crash silently. see: DebugUtil::DisableOSCrashDumps() in base/debug_util_mac.cc Best regards, Jeremy On Tue, Nov 10, 20

[chromium-dev] Core Text

Re http://crbug.com/27195 & https://bugs.webkit.org/show_bug.cgi?id=31802 : Dan Bernstein says that Core Text on Leopard has performance issues vs ATSUI so I'm going to look into switching APIs at runtime rather than compile time. So we'd use ATSUI < 10.6 & Core Text >= 10.6 . Best regards, J

Re: [chromium-dev] Core Text

again, MacVim doesn't do very complex text rendering). > > (Source: > http://groups.google.com/group/vim_mac/browse_thread/thread/b93c6dd5183bdc5e > ) > > On Mon, Nov 23, 2009 at 12:58 PM, Jeremy Moskovich wrote: > >> Re http://crbug.com/27195 & https://bugs.webkit.

Re: [chromium-dev] Core Text

ds, > > Hironori Bono > E-mail: hb...@chromium.org > > On Tue, Nov 24, 2009 at 6:17 AM, Jeremy Moskovich > wrote: > > Thanks Nico, > > I'll run some numbers. > > Best regards, > > Jeremy > > > > On Mon, Nov 23, 2009 at 11:15 PM, Nico Weber

Re: [chromium-dev] Core Text

feel free to revert this CL (just drop me an email with a link to the bad run if you do so, please). Thanks, Jeremy 2009/11/24 Jeremy Moskovich > Thanks Hironori, > > I thought so too at the beginning but it turns out that they are available, > just not declared in public headers. Th

Re: [chromium-dev] Core Text

ac10.5%20Perf%281%29/builds/6289/steps/page_cycler_intl2/logs/stdio > > > http://build.chromium.org/buildbot/perf/mac-release-10.5/intl2/report.html?history=150 > (my DEPS roll was 33776) > > I'm going to revert. > > -atw > > 2009/12/3 Jeremy Moskovich >

Re: [chromium-dev] Core Text

hould also have the effect of fixing [or modifying the stack traces] we've been seeing for ATSUI crashes on 10.6. Best regards, Jeremy 2009/12/4 Jeremy Moskovich > Thanks Drew, > > I'll look into toggling ATSUI/Core Text at runtime based on OS version > then. > > Be

Re: [chromium-dev] Core Text

*10.6.2 <-> 10.6 2009/12/14 Jeremy Moskovich > OK, the runtime switch has landed in the WebKit tree as > http://trac.webkit.org/changeset/52067 . We should pick it up next time we > roll deps. > > There should be no perf regression this time since we'll continue to us

Re: [chromium-dev] Core Text

Even if there is a perf regression, we have to take it if we want to get > correct rendering. > > Avi > > On Mon, Dec 14, 2009 at 10:32 AM, Mike Pinkerton > wrote: > >> 2009/12/14 Jeremy Moskovich : >> > There should be no perf regression this time since we&#x

Re: [chromium-dev] Core Text

I'll put together some numbers. Best regards, Jeremy On Mon, Dec 14, 2009 at 6:46 PM, Mark Mentovai wrote: > Jeremy Moskovich wrote: > > Yep, Avi's right - we don't really have that option here. ATSUI is > > deprecated in 10.6 - we're seeing crashes and in

Re: [chromium-dev] Core Text

ually represent interesting numbers. The extra speediness in 10.6 ATSUI may be due to it ignoring certain parts of the font hinting data leading to the bug this is all in place to fix. Best regards, Jeremy On Mon, Dec 14, 2009 at 6:46 PM, Mark Mentovai wrote: > Jeremy Moskovich wrote: > > Ye

Re: [chromium-dev] layout-test outputs and spell-checker

Hi Horonori, Thanks for taking a look at this!! What kinds of differences are you seeing without the new spellchecker class? The only notable difference seems to be that the fonts are slightly different vs. the expected output. Where is the expected output coming from? What OS version are you

r35237 rolled back - was [chromium-dev] buildbot failure in Chromium on Chromium Mac, revision 35245

FYI: I rolled back r35237 to fix the build. http://src.chromium.org/viewvc/chrome?view=rev&revision=35237 broke the Mac unit tests ( http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Mac/builds/3792/steps/unit_tests/logs/stdio ). Specifically FontLanguageSettingsControllerTest, it

Re: [chromium-dev] Re: Running Chromebot on official builds from trunk

Driveby [possibly irrelevant] comment: I committed a patch to trunk after the beta branch that changes the code path for reaping processes, you might want to try to repro this on the beta branch and then try on trunk. On Thu, Dec 31, 2009 at 7:33 AM, Mark Mentovai wrote: > Debugging tips: > > 1.

[chromium-dev] OS X Sandbox design doc updated

Hi, I've updated the OS X Sandboxing design doc to better reflect the current state of affairs. Edits/corrections are welcome. Best regards, Jeremy -- Chromium Developers mailing list: chromium