80407 - browser won't start - claims it needs OLEACC.DLL

Status: RESOLVED FIXED

(Core :: XUL, defect)

Description

[John Bandhauer]

In my NT4 debug build I get a 'Can't find DLL dialog' and the app aborts (with a 
threadsafety assertion thrown in for good measure).

This is a blocker for me.

Comment 1

[John Bandhauer]

Apparently the first (and maybe only?) dll with this implicit link to 
OLEACC.DLL is gkwidget.dll. dumpbin /IMPORTS gkwidget.dll indicates that only 2 
entries are imported:

   OLEACC.dll
             10048CC0 Import Address Table
             100482FC Import Name Table
                    0 time date stamp
                    0 Index of first forwarder reference

                  D  LresultFromObject
                  3  AccessibleObjectFromWindow

This reinforces my thought that this could be LoadLibrary/GetProcAddress 
dynamically linked with silent failure.

Comment 2

[Peter Trudelle]

Installing MSAA SDK from URL above should be a quick/dirty workaround for this,
we are working on a better solution. cc aaronl

Comment 3

[John Bandhauer]

I see in lxr only one call each to the two functions here.

I'd try to abstract these suckers. Removing oleacc.lib from the makesfiles would 
keep you honest when you do force these to be explicitly loaded.

So, what should be the criteria for forcing these things to be loaded? Whos 
needs then - certainly not everyone. How does the app know that they are 
needed?

Comment 4

[John Bandhauer]

The fix you checked in worksforme.

Comment 5

[Eric Vaughan]

This is fixed. It now used LoadLibray and get the library only when needed. It 
also gracefully fails if the library can't be found.