Closed
Bug 295257
Opened 20 years ago
Closed 19 years ago
eCare plugin v 2.0.3 causes hang of all Mozilla browsers on OS X
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 299437
People
(Reporter: jonesy, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-gb) AppleWebKit/412 (KHTML, like Gecko) Safari/412 Build Identifier: I have been stuck recently unable to use Firefox, Camino or Mozilla. I had tried everything until I thought of my Internet Plugins. The Netopia eCare plugin was the only thing on the computer that crashed all the time and not on my other. Removing it has restored normal behaviour. Reproducible: Always Steps to Reproduce: 1. Open any Mozilla based Browser 2. Immediately crashes 3. Actual Results: Talkback opens Expected Results: Opened
Comment 1•20 years ago
|
||
Can you provide the Talkback ID please? Talkback is located in the /components directory.
| Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1) > Can you provide the Talkback ID please? > > Talkback is located in the /components directory. Sorry, I can't. If I try to open Firefox with the Plugin installed it locks up the computer completely and I have to restart. I have had to trash the plugin altogether.
try using activity monitor, select the mozilla creature, go to threads and select sampler. attach the output of sampler.
Assignee: nobody → zack
Component: General → Ports: Qt
Product: Firefox → Core
QA Contact: general → cbiesinger
Summary: eCare plugin v 2.0.3 causes crash of all Mozilla browsers on OS X → eCare plugin v 2.0.3 causes hang of all Mozilla browsers on OS X
Version: unspecified → Trunk
Assignee: zack → nobody
Component: Ports: Qt → Plug-ins
QA Contact: cbiesinger → plugins
There's an actual crash log from Camino 0.9a1 in bug 299437, so duping.... *** This bug has been marked as a duplicate of 299437 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•