Closed
Bug 3429
Opened 26 years ago
Closed 26 years ago
unhandled exception
Categories
(Core Graveyard :: Embedding: ActiveX Wrapper, defect, P1)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: martind, Assigned: locka)
Details
When I include the Mozilla Active X control in VB 5 SP3, I get an unhandled
exception and VB blow up. The unhandled exception occurs when I include the
object in a form. So just after having created the boundary rectangle that
should contain the object in the form, the errors occurs. I set the PATH
variable to the directory containing all the Mozilla compnents before trying to
use the control. The error happened with the new renamed control (build 030399)
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Without further information I can't resolve the problem. I frequently test the
control in my environment without incident.
If you can provide me with a sample HTML file, I can test it out.
"The problem does not occur with a particular HTML document. As stated in the
bug report, the problem occurs when the Active X object is instantiated in a
Visual Basic Form. The problem happened at design time. The object could not
be instanciated at design time, an exception error occured. So no needs for
a HTML document, it blast long before being able to navigateTo a particular
document." - Didier PH Martin, martind@netfolder.com
locka or martind, if you could please verify this as fixed in a current build,
i'd very much appreciate it... i don't have the tools to verify this. thanks,
cpratt
Comment 4•26 years ago
|
||
I forgot to mention -- the same behavior is exhibited in 4.5
Comment 5•26 years ago
|
||
ignore my previous entry -- for some reason I ended up in this bug and not the
bug I was working on -- sorry!
given that the bug reporter has not provided feedback, I am marking this as
verified worksforme.
I can't reproduce this bug. I just opened VB6, inserted the Mozilla control
onto an empty form and repeatedly ran/stopped it to see if I could crash it
which I couldn't.
There used to be a problem with doing this because NS_SetupRegistry was called
multiple times and crash VB. It could be that this bug has since been fixed in
the NSPR causing the control to behave properly.
Updated•13 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•