Closed
Bug 98721
Opened 24 years ago
Closed 24 years ago
TestGtkEmbed fails to luanch with seg fault (core dump)
Categories
(Core Graveyard :: Embedding: APIs, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tracy, Assigned: adamlock)
Details
(Keywords: smoketest)
Attachments
(1 file)
seen on TestGtkEmbed 2001-09-07-06-trunk
-Install the build
-launch it
it fails to start up with just a seg fault message and (core dump) on the
console
| Reporter | ||
Comment 1•24 years ago
|
||
this is blocking the memory usage test. perhaps this is also the reason for the
increased leakage? go to
http://ftp.mozilla.org/pub/data/PerformanceAndFootprints.html
to see graphical results of these tests.
Note: The improved tag on the memory test is a obviously incorrect. Don't we
all wish the app could use zero memory. I've resubmitted the data to this page
it should only take a few minutes before it is updated to the world.
Keywords: smoketest
mfcEmbed and PPembed have problems too.
I suspect it is something to do with recent component manager changes because
the component.reg file is not being created correctly.
Investigating further.
CC'ing Doug.
NS_InitEmbedding is calling NS_InitXPCOM2 which is returning a nsnull
nsIServiceManager in the first argument. This makes NS_InitEmbedding unhappy so
it is returns an error code.
I will try and hack a patch around this, but I need to know if this new
behaviour is deliberate or not. From inspecting our embed api code I think we
could (and should) switch over to the do_QueryService method.
Comment 6•24 years ago
|
||
sr=blizzard
The larger bug needs to be fixed, though. Please don't let it fall through the
cracks.
Fix is checked in. Bug 98735 opened to deal with the issue of whether
NS_InitXPCOM2 even needs that argument anymore.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 8•24 years ago
|
||
verified fixed on linux TestGtkEmbed 2001-09-07-11-trunk
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•