Closed Bug 243357 Opened 21 years ago Closed 21 years ago

M17rc2 Flash related crashes [@ libflashplayer.so]

Categories

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 200511

People

(Reporter: tor, Unassigned)

References

()

Details

(Keywords: crash, topcrash)

Crash Data

In the 1.7rc1 talkback data libflashplayer.so is the top crasher, and also appears in the call stack for a number of second most frequent crasher. Looking at the stacks, while the portion above libflashplayer.so changes, it seems to crashing at two points in the flash plugin: libflashplayer.so + 0xef347 (0x457ef347) [5 frames in flash] and libflashplayer.so + 0xe006d (0x421a006d) [7 frames in flash] Win32 rc1 is also having flash crashers - bug 202968.
Keywords: crash
I'm guessing these are the same types of crashes we're seeing on Windows under NPSWF32.dll. Should we just mark this a dup of bug 202968 and track Flash crashes for both platforms in one bug? Updating summary for now: M17rc1 -> M17rc2
Keywords: topcrash
Summary: M17rc1 Flash related crashes [@ libflashplayer.so] → M17rc2 Flash related crashes [@ libflashplayer.so]
Depends on: 211213
*** Bug 249713 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 217296 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 200511 ***
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → DUPLICATE
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-flash
Target Milestone: --- → 2004
Version: Trunk → 6.x
Crash Signature: [@ libflashplayer.so]
Version and milestone values are being reset to defaults as part of product refactoring.
Target Milestone: 2004 → ---
Version: 6.x → unspecified
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.