Could not start google chrome normally about gdipp HOT 40 CLOSED

Can you tell me the version and bitness of your Chrome? I want to make sure it 
is
32-bit, because gdipp uses an assembly code snippet to inject gdimm, which is
supposed to work only for 32-bit Chrome.

I can start and render new tabs and close normally in my Windows 7 64-bit + 
Chrome
5.0.342.3 32-bit. As far as I know, there is no official 64-bit release for 
Chrome.

4.1.249.1036 beta (41514)
I'm not very sure what bitness it is. Judging from windows task manager it 
should be 
32-bit
I might try 5.x beta later on

Tried it on 5.0.356.0 beta, still having the same thing (could not close error)

It happened to me once, but after I close Chrome and restart, the problem is 
gone. I
still do not know how to stably reproduce the problem.

[deleted comment]

I second the same error. And that error occurs only once.

But I can use chrome, after a second start, no problem.

I am using 0.7

Now google chrome (5.0.356.2) crashes surely.  

I confirm that on chrome 5.0.356.2, with gdipp 0.7 service installation, it 
still 
produces the same error. After closing and restarting chrome it works fine.
However CPU usage is high with windows service method, wmiprese.exe is eating 
up ~15% 
of CPU constantly.
Registry method works fine as a whole. In previous gdipp versions I get 
"Internet Low-
Mic utility has stopped working" (ielowutil.exe) error from time to time. None 
so far 
with 0.7 yet. Finger crossed :/

Latest 0.7.1 x64 still crashes google chrome. It's really sad that chrome is 
totally
unusable. 

Chrome still crashes on 0.7.1, but it's hardly unusable.  Usually just crashes 
for me 
on first load after a reboot, SOMETIMES but not often again during the same 
uptime.

Closing it and opening it again usually equals it working fine.

For the past few days I have been using 0.7.0 (the one that was pulled off) 
with 
registry setting, and everything works fine for me
Chrome starts normally, and no more ielowutil.exe error that I got before

I am using chrome 5.0.356.2. After a clean install with no extension, chrome 
stops
crashing.

As I guessed before, it may be the problem of addon system.

Changed to registry mode with 0.7.1 and it's stopped crashing.

This is quite a buggy build, hopefully a new dev build today.

I am sorry to ask an off-topic question:

The most useful parameters of gdipp is text embolden and text shadow. Is the 
function inherited from freetype or implemented in gdipp. I am using archlinux 
and the text look too slim. Where can I find the parameters to tune text 
weights 
and shadow?

Embolden is done by the FreeType function FT_Outline_Embolden
(http://freetype.sourceforge.net/freetype2/docs/reference/ft2-outline_processing
.html#FT_Outline_Embolden).
Shadow is implemented by gdipp. To embolden, apply the function on the glyph 
outline
before rendering to bitmap. To make shadow, draw the bitmap with offset and 
alpha first.

Thanks for the enlightment!

Have you considered using existing cairo library to do high level graphic 
rendering,
like text shadow. Direct2D backend for cairo is also in development.

I considered Cairo before starting the project. However, I think directly 
calling API
should outperform Cairo with respect of rendering performance. Besides, there 
will be
more dependencies switching to Cairo.

I have never had a problem with Chrome and gdimm when running with 
"--no-sandbox".  
Ideally of course the sandbox should work too, and I will occasionally try new 
combinations of Chrome devel builds and gdimm but so far this is the most 
stable way to 
get it to work. 

Finally with 0.7.3, chrome stops crashing. The only problem is lagging when 
using google reader and gmail. 
All setting default.

If you switch items very fast in Google Reader, it is indeed you can notice the 
lag.
We are constantly optimizing the performance, however there is no free meal. 
Good
glyphs come at a cost. Also, gdipp is user-space module. In order to access
kernel-space objects such as HDC, overhead is inevitable.

Chrome has started crashing for me again on 0.7.4 :(

Can't use the registry method just now as it stops text appearing in LastFM.  I 
just 
exclude it with services mode.

me too with 0.7.4

wired action with chrome, just exclude it.

With cache introduced in 0.7.5, lag in gmail and google reader is totally gone! 
Wonderful work:)

Nice to hear. You can further increase "cache_max_bytes" setting for larger 
glyph
cache size.

Nice advice~, I change the size to 20,000,000. Now everything is even smoother 
and faster. However, I still 
get the annoying error dialog when starting chrome after every restart of 
windows... the old problem 
though. 

Issue 46 has been merged into this issue.

Issue 63 has been merged into this issue.

this issue exist only at x64 system. on x86 work fine for me.

same problem using gdipp 0.8 and chrome 6.0.422.0

register method eliminates the problem. x64 with 0.8.1

I'm using as service (0.8.1) and after a first error now it seems to work ..

Register method is the most stable!

Registry method does avoid the Chrome issue. What's the downside of using the 
Registry method? What exactly are missing versus the Service method?

First, the registry method (writing the AppInit_DLLs value) is not recommended 
by Microsoft. Although it is still available in Windows 7, it may be removed in 
future versions. Second, the registry method is system-wide without 
discrimination. This means critical system processes such as csrss.exe, 
smss.exe are also injected the gdimm DLL, which potentially threatens system 
stability. Third, you cannot cancel gdipp's render during system uptime. There 
is no way to unload gdimm DLL from injected processes until their termination. 
On the contrary, stopping service automatically unloads gdimm DLL from all 
inject processes, since the injection mechanism is controlled by the service 
itself.

If you find all these reasons trivial, registry method is good for you.

what about this issue using 0.8.2 ?

Rendering is perfect in my case. I don't know if the csrss error message still 
exists. At least I haven't encountered any.

work fine now.

same issue. can't load tabs in chrome after running gdipp services.
using:
vista x64.
chrome 12 stable version.
gdipp 0.91 beta.

chrome still load tabs but I can feel a big lag.
using: win7 x64
gdipp 0.91 beta.