Closed Bug 36571 Opened 25 years ago Closed 25 years ago

Crash trying to load realaudio page, manually added plugin from earlier installation

Categories

(Plugins Graveyard :: RealPlayer (Real), defect, P3)

x86
All
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: shrir, Unassigned)

References

()

Details

(Keywords: crash)

This crash is on Realplayer. Am logging this as a seperate bug. I placed the real plugin file from 4.x installation to plugins folder on mozilla. Trying to view this page causes a crash. Stack trace: Trigger Type: Program Crash Trigger Reason: PowerPC unmapped memory exception Call Stack: (Signature = PLUGIN_DLL + 0xfc60 (0x0ba32a10) a53c1713) PLUGIN_DLL + 0xfc60 (0x0ba32a10) RealPlayer Plugin + 0x5f4 (0x0a96e674) PNMM.lib + 0x2fc (0x0ba0d73c) PNMM.lib + 0x700 (0x0ba0db40) PNui50.Lib + 0xfc (0x0a0298cc) PNui50.Lib + 0x538 (0x0a029d08) PNui50.Lib + 0x34b84 (0x0a05e354) RealPlayer Plugin + 0x1870 (0x0a96f8f0) RealPlayer Plugin + 0x7f8 (0x0a96e878) RealPlayer Plugin + 0x11d0 (0x0a96f250) PLUGIN_DLL + 0x220c (0x0ba24fbc) PLUGIN_DLL + 0xa244 (0x0ba2cff4) PLUGIN_DLL + 0x908c (0x0ba2be3c) PLUGIN_DLL + 0x8644 (0x0ba2b3f4) LAYOUT_DLL + 0xdaa9c (0x0a1c39cc) LAYOUT_DLL + 0xda024 (0x0a1c2f54) LAYOUT_DLL + 0x2168b8 (0x0a2ff7e8)
Adding crash keyword.
Keywords: crash
Nominating nsbeta2. RealPlayer is one of the plug-ins that must work for nsbeta2 per the beta2 criteria.
Keywords: nsbeta2, realplayer
Is this due to plugin or installation code?
Whiteboard: [NEED INFO]
Shrirang, could you please determine whether this happens with a proper install?
This is not happening anymore. ( no crash, but bug 19931 still shows). Marking this WFM (build 2000052208)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
verified (2000071708)
Status: RESOLVED → VERIFIED
OS: All
Assignee: serhunt → nobody
Component: Plug-ins → RealPlayer (Real)
Product: Core → Plugins
QA Contact: shrir → real-player
Whiteboard: [NEED INFO]
Version: Trunk → 5.x
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.