588218 - Custom C++ plugin freezes when making COM API call in 3.6.2 - 3.6.8

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[David Clark]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729)

I have a custom plugin, written in C++, which access Quickbooks through Quickbooks' COM based integration API.  This plugin works fine for all versions of Firefox before 3.6.2.  It does not work in any of the stable versions after that, including 3.6.8.  I have verified that this problem is NOT in the latest 4 series beta build.  The ActiveX version of this plugin (for Internet Explorer) which shares the same code base also works fine on the latest version of IE.

When the plugin calls the BeginSession method, using the Quickbooks API, the method call just freezes.  I have confirmed this by running the plugin under a debug session.

I can provide code and access to help reproduce this bug, but if you don't have Quickbooks it will be of little use.  I am a developer, and I am familiar with COM programming, so I may be able to help in pinpointing the problem.

Reproducible: Always

Steps to Reproduce:
1. Access page that uses plugin
2. Plugin freezes

Actual Results:  
Plugin Freezes.


This is a plain vanilla Firefox installation.

Comment 1

[Nickolay_Ponomarev]

Hi, do you mean XPCOM component or an NPAPI plugin?

In any case you could try finding someone who can help you on irc.mozilla.org (#developers) or in the appropriate newsgroup.

Since this changed between Firefox versions, it will probably be useful to know what change caused this -- see http://new.quality.mozilla.org/documents-home/bugs-docs/bug-triaging-guidelines/finding-regression-windows - you'll need "-mozilla-1.9.2" directories with 3.6.2a|b|pre files.

Comment 2

[David Clark]

It is an NPAPI plugin.

Comment 3

[timeless]

david: https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to timeless from comment #3)
> david: https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

Comment 5

[David Clark]

I have no idea if this bug is still around and I have no way of reproducing it.  This bug was an absolute show stopper and it forced be to rewrite an entire application since nobody cared about the bug when I first filed the report (and I had insufficient knowledge to fix it).

Comment 6

[Wayne Mery (:wsmwk)]

thanks for the update.
no testcase and no stacktrace, so => incomplete