Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Why does Firefox get into an infinite loop for "mac_plugin_interposing_child_OnShowCursor"?

  • 25 freagra
  • 1 leis an bhfadhb seo
  • Freagra is déanaí ó DICKGUERTIN

more options

I get infinite loops in Firefox from certain webpages. I tried Safe-Mode, and couldn't even get to the main site causing an infinite loop in Firefox (Apple Bug Reporter), but could get there in Chrome or Safari. I used Activity Monitor to Get Info for Firefox, and then took a Sample. There were 375 instances of "mac_plugin_interposing_child_OnShowCursor", along with 107 instances of "DumpCompleteHeap". This problem is occurring on three separate Macs running the same or different versions of Firefox. One is 10.5.8 (Leopard) with FF 16.0.1. The other two are Mac 10.6.8 and Mac 10.10.5, each running FF 41.0.2 (latest FF). This infinite loop has also occurred in at a site where I was trying to view a doctor's profile. I have a 1647 line Sample.Firefox.txt that shows what happened in Safe-Mode attempting to get to Apple Bug Reporter. That file is 217Kb in size, and I'm willing to attach it to an email to Mozilla.

All Replies (5)

more options

I thought THIS was a bug report. You're asking me to "file a bug report", which is what I've done HERE. As for "comment in bug reports", are you implying this IS a bug report? All I'm trying to do is assist in the analysis of the bug, which clearly is in Mozilla's code for an OSX product: Firefox for Mac.

This is a "" page, so why are you quoting me a "" page? I'm looking for SUPPORT, but if I have to start all over again with Bugzilla, then someone needs to explain WHY and HOW.

more options

My apology to all of you. I just discovered this on the General.Mozilla etiquette page: Report bugs in Bugzilla, not in the Mozilla forums.

Therefore, I'll start over with Bugzilla, and try to include some of the documentation via a personally constructed web page, and point them at it.

Sorry if I offended anyone; I'm was just looking for a solution to a problem.

more options

This is a random thread on a support forum as it is not really a place to track bugs.

A good idea to talk about issue(s) here first though before filling a report or commenting in existing report in bugzilla.

The is a general issues tracker for a variety of things Mozilla related whether about * pages, products, project or other things as actual bugs with something only makes up a part of the number of bug reports. The etiquette page is to help minimize "Me too" "why is this not fixed!!!" kind of comments as that can make those who can fix it to look at other reports instead in meantime.

more options

Thank you, James. I appreciate your comments. I've taken a rather simple approach... I've created a webpage, that anyone can access, that describes the "problem".

I've then initiated a Bugzilla bug report which points them at that page, and provides them with ways to contact me. I'll see how that goes.

more options

To all following this thread.... This may be a bug in Apple Bug Reporter, and I've created two webpages associated with this problem. There are at:

The 1st is the bug report I files with Bugzilla, but this might be a problem in Apple Bug Reporter, so I created ABR.html to support that possibility. I'm leaning toward ABR as the source of the problem.

  1. 1
  2. 2