Mac OSX: Error received in message reply handle + Internals of CFAllocator not known

[and...@nocte.co.uk]

Hi,

I just started to implement berkelium in my app, I managed to compile and link the libraries, but I'm still having some issues that I can't understad. does anybody have any clues of what's going on? (chrome bug report doesn't make much sense to me)

2013-03-28 11:13:23.666 berkelium[2682:707] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650

2013-03-28 11:13:23.723 berkelium[2682:1203] Connection Invalid error for service com.apple.hiservices-xpcservice.

2013-03-28 11:13:23.723 berkelium[2682:707] Error received in message reply handler: Connection invalid

2013-03-28 11:13:23.723 berkelium[2682:707] Error received in message reply handler: Connection invalid

2013-03-28 11:13:23.730 berkelium[2682:707] Error received in message reply handler: Connection invalid

2013-03-28 11:13:23.731 berkelium[2682:707] Error received in message reply handler: Connection invalid

2013-03-28 11:13:28.804 berkelium[2686:707] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650

2013-03-28 11:13:28.805 berkelium[2685:707] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650

[Ewen Cheslack-Postava]

It sounds like Chrome is inspecting internal state in the memory
allocator in order to handle some error conditions, but that means any
time the implementation of the memory allocator changes, the Chrome
code also needs to be updated to support it.

Unfortunately, that probably means there's a patch somewhere in the
Chrome history that *might* apply to the current version we have that
would make it work on whatever version of OSX you're using. But you'd
have to dig that up and backport it... Searching for commits that
include issue 45650 in their commit log might be the first thing to
try.

-Ewen

> --
> You received this message because you are subscribed to the Google Groups
> "Berkelium" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to berkelium+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[and...@nocte.co.uk]

is that related with the CFAllocator issue or the invalid connection?

I'm asking because I get the CFAllocator message with Awesomium as well, so that shouldn't be too critical(the sample works).

thanks

Andrea

[Ewen Cheslack-Postava]

Ah, I see. The other message I don't know about. We have one mention
of it in Sirikata's IRC logs:
http://sirikata.com/irc/logs/freenode/%23sirikata/2012-06/%23sirikata.05.log
but not a resolution. I haven't really done anything with Berkelium on
Mac recently so I don't know what the quality level is.

Also this Chromium bug report might be helpful:
http://code.google.com/p/chromium/issues/detail?id=127973 . Might be
some issue with bad cache state. Unfortunately, even if some of these
issues were resolved, we're far enough behind current Chromium that it
would still pop up in Berkelium.

Did you build the demos included with Berkelium, and do they work
without this message? It could be helpful to know whether this is an
issue with Berkelium/Chromium or just with the way you currently have
it integrated with your project.

-Ewen