170864 - NS_InitEmbedding failing in both gre and non gre env for mfcembed

Status: RESOLVED FIXED

(Core Graveyard :: Embedding: APIs, defect)

Description

[Ashish Bhatt]

AutoRegister method in NS_InitEmbedding failing in gre and non gre enviornment.
It also fails when NULL is passed to NS_InitEmbedding.

Comment 1

[Matthias Versen [:Matti]]

*** Bug 170863 has been marked as a duplicate of this bug. ***

Comment 2

[Matthias Versen [:Matti]]

*** Bug 170866 has been marked as a duplicate of this bug. ***

Comment 3

[Chak Nanga]

I'm unable to repro in my latest MfcEmbed builds.

I tested with my latest Mozilla trunk build of MfcEmbed in both the GRE and
non-GRE envs and i do not see any failures. I can run MfcEmbed fine and can view
web pages etc.

Let's get the latest nightly embed-win32.zip and also the GRE builds and test it
on a machine other than the one where Ashish is noticing the error - just to
isolate if there's something wacky going on Ashish's machine.

Comment 4

[Charles Rosendahl]

reassigning to Ashish to verify if this is still present.

Comment 5

[Matt Collins]

hi there, just thought i'd try and throw some extra light on this one - it seems
that the problem depends mainly on the availability/accessibility of certain
folders. running mfcembed.exe from its own folder
("...\embedding\tests\mfcembed") gives me a variety of errors, but running it
from "...\dist\bin" is fine (it does assert on shutdown but that's not relevant
here).

i'm still finding my way around the massive code tree (the first time i saw
mozilla source was a couple of weeks ago) so i'm afraid i can't get you more
(useful) details, but for what it's worth, it seems it's both the dll's in the
"dist\bin" as well as the folders below, especially "dist\bin\defaults" - if i
rename it (to hide it from mfcembed), mfcembed throws loads of asserts before
gpf'ing... hiding other folders does cause some asserts to fire but it does
manage to render the default webpage. 

anyway, hope this helps :)

Comment 6

[Benjamin Smedberg]

I'm pretty sure this got fixed with bug 223900, along with a lot of other stuff.