Closed Bug 159575 Opened 22 years ago Closed 19 years ago

browser crashes with gtk cast error with SVG plug in

Categories

(External Software Affecting Firefox :: Other, defect, P3)

Sun
Solaris
defect

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: peterb, Assigned: srgchrpv)

References

()

Details

(Keywords: crash, Whiteboard: [PL2:NA])

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1a) Gecko/20020614
BuildID:    2002061401

Gtk-WARNING **: invalid cast from `GtkText' to `GtkMisc'

Gtk-CRITICAL **: file gtkmisc.c: line 204 (gtk_misc_set_padding): assertion
`GTK_IS_MISC (misc)' failed.
EULA: 1

I probably need to understand more about what GTK is doing here,
I downloaded to use GIMP and it usually is stable. However, I may
have a change management problem in my versioning of GTK since
I started out building it from source, and then may have gone
back to the binary. Never the less,the SVG Solaris Plug in for
Mozilla appears to work ok for the static svg file in the test kit,
but when I access the plug in, that's where it consistently crashes.

Reported to Adobe on their bug page.

I noticed the other bug reports on SVG, and apparently it's a low
priority at this point, (it appears to crash consistently).

Not sure about two points.

Classes of accepted plugins.

Unforced interfaces? I think was the term.

 

Reproducible: Always
Steps to Reproduce:
1.install SVG plugin (create symlink in /usr/local to actual location)
2.accept Eula
3.restart browser
4.be confused about what version of GTK you actually have
5.try to find out the relevant lib that was installed for GTK
5.5 copy shared libs to /usr/lib
6.try test page in kit, (works with some additional cruft) nice!
7. Go to adobe SVG site
8. Crash browser
9. Repeat as needed.


Actual Results:  was able to view static SVG in adobe directory
was able to crash browser using adobe site

Expected Results:  hard to say where the problem is, but the bugzilla list
points to structure of the plug in not being conformant.

if that's the case, then I can't expect mozilla to do much
about it, and it's an adobe problem. or a gtk problem.

http://mail.gnome.org/archives/gtk-devel-list/2001-March/msg00683.html
has some notes about changes to gtk padding.
SVG is 3.0 Beta Release 1, Build 77
Severity: minor → critical
Keywords: crash
dup of bug 133567 ? It's in the release notes but for some reason listed as
under Windows. The bug itself is OS: All.
I would not call this an exact duplicate of 133567, but I'm not
sure what new this adds to an already long list. It does
not crash with most of the w3c and other example, but it does
on the adobe site which initially loads the eula.

-pb
can you run mozilla in gdb or similar and get a backtrace of the crash yous see?
I was using the binary, running it in GDB doesn't show much. I tried
building the mozilla source with debugging, but I can't get configure
to ignore LibIDL, got the LibIDL
source from Gnome, tried building it, it in turn required flex,
got flex 2.54a, and flex consistently seg faults either in my
native copiler for solaris 8, sparc 64, or gcc. If I could
build the source, I think I could make some progress.Might try
it on Linux.
I sent Serge a sidenote on this and he believes this is not a dup of bug 133567,
he said it looks like it may be a gtk or X related problem. Assigning to Serge
for debugging.
Assignee: beppe → serge
Priority: -- → P3
Whiteboard: [PL2:NA]
Target Milestone: --- → mozilla1.2alpha
I donwloaded the Adobe SVG viewer from:
http://www.adobe.com/svg/viewer/install/old.html
And get the same results.
With mozilla (win2k, build 2002091014) I can look at local .svg files, but if I
create an html file with the embed tag such as in
http://www.privasphere.org/bugs/mozilla/embedKiller.html
my browser crashes.
I downloaded the latest adobe svg viewer just today.
svg used unfrozen interfaces, so even if we fixed this issue, you will still
crash because of bug 133567. Moving to future and setting dependency
Depends on: 133567
Target Milestone: mozilla1.2alpha → Future
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Component: Plug-ins → Other
Product: Core → Plugins
Target Milestone: Future → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.