Closed Bug 409566 Opened 13 years ago Closed 8 years ago
Adblock and Java applet are crashing - infinite recursion in plugin
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 At least for me, and I tried this several times including after a reboot, attempting to run Secunia's software inspector in FF 3 Beta 2 crashed. Reproducible: Always Steps to Reproduce: 1. Open Page 2. Go through screens. 3. Actual Results: Crash Expected Results: Run Secunia Inspector to completion.
works for me - Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2007122105 Minefield/3.0b3pre
Based on the fact that it worked for you, I had an idea and it panned-out. I am not a programmer, or anything, but I tried to run Secunia after disabling the Ad-Blocker Plus add-on. That did the trick. So that's where the conflict appears to be.
I can confirm this crash with : Mozilla/5.0 (Windows; U; Windows NT 6.0; rv:1.9b3pre) Gecko/2007121403 SeaMonkey/2.0a1pre Java Plug-in 1.6.0_03 Adblock Plus 0.7.5.3 There is somewhere a different bug report about another applet with the same problem
Severity: normal → critical
Status: UNCONFIRMED → NEW
Component: General → Extension Compatibility
Ever confirmed: true
QA Contact: general → extension.compatibility
Summary: Crash → Adblock and Java applet is causing crahses
Summary: Adblock and Java applet is causing crahses → Adblock and Java applet are crashing
You get a security warning from java if you Start the Scan, if you confirm it you get a crash, if you store the selection (always trust ..) it seems to work on the next time without crash. My crashreporter seems to be unhappy to send the report at the moment...
I also encountered the problem with crashreporter not functioning each time I crashed. However, at least with my configuration, I did not receive the security warning from Java before starting the scan or a crash caused by Java. My only conflict is with AdBlocker, which I was able to resolve by merely adding Secunia to the disable Adblocker list. My hunch is the difference between my experience with Java and Mattias's is perhaps that he has never used Secunia before.
Report it to the developer of the extension. I am not sure if you used adblock or adblock plus so here are links to each forum. http://adblock.mozdev.org/forum.html/no_wrap http://adblockplus.org/forum/
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Sorry for the confusion, it is AdBlocker Plus.
1138 CallWindowProcAorW 1139 CallWindowProcA 1140 jpinscp.dll@0x3788 1141 InternalCallWinProc 1142 UserCallWinProcCheckWow 1143 CallWindowProcAorW 1144 CallWindowProcA 1145 PluginWndProc d:\builds\tinderbox\seamonkeytrunk\winnt_5.2_depend\mozilla\modules\plugin\base\src\nspluginnativewindowwin.cpp:357 1146 InternalCallWinProc 1147 UserCallWinProcCheckWow 1148 DispatchClientMessage 1149 __fnINOUTLPSCROLLINFO 1150 ntdll.dll@0x60e6d 1151 nsView::DoResetWidgetBounds(int, int) d:\builds\tinderbox\seamonkeytrunk\winnt_5.2_depend\mozilla\view\src\nsview.cpp:411
Status: REOPENED → NEW
Component: Extension Compatibility → Java: OJI
Product: Firefox → Core
QA Contact: extension.compatibility → java.oji
http://www.z-u-l.de/doc_en/Tutorial/tut-2-1x.html seems to be another occurrence of the same bug. It crashes for me every time I reload the page, stack (http://crash-stats.mozilla.com/report/index/ef3af2e8-c55e-11dc-aa10-001a4bd43ef6?date=2008-01-18-00) looks very similar to the one quoted above. Note that this page works fine in Firefox 184.108.40.206 - Adblock or not.
I can confirm the crash of Firefox 3 Beta 3 Portable (PortableApps) with Adblock Plus 0.7.5.3. When ABP is enabled, the crash occurs even if it's disabled on Secunia address. When ABP is NOT enabled, the crash doesn't occurs.
for reference, "disabling" an extension for a url doesn't prevent it from running on the url, it merely asks it to do as little work as possible when it hits the url. which is why being disabled for secunia but not disabled is just as likely to crash as enabled in general as long as the problem is on the gecko side of things :).
Summary: Adblock and Java applet are crashing → Adblock and Java applet are crashing - infinite recursion in plugin
This problem also occur with Noscript Estension release 1.5.6 and Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 ID:2008032620 Ciao
Johnny, can you take a look at this bug and bug 422324 which is likely the same? Judging by the stack in 422324, this looks like it's the number 23 topcrash for Firefox 3. Is there anything we can do here?
Mats, any chance you could look into this recurse to death bug?
Assignee: nobody → mats.palmgren
Priority: -- → P2
Sorry, can't reproduce it. Tried both Firefox 3.0 final and a local 1.9.0 debug build on Windows XPSP2, using Java Plug-in 1.6.0_07 + Adblock Plus 0.7.5.5 + NoScript 1.7.6 (currently the latest versions). The Secunia inspector runs to completion and the Java Applets in comment 14 works fine, even when running them at the same time in different tabs, running several applets in different tabs/windows, reloading pages, closing tabs and windows etc... no problem. I tried the following add-on combinations: ABP ABP + NoScript NoScript (the URL in comment 11 is dead so couldn't test it)
Assignee: mats.palmgren → jst
(In reply to comment #19) > [...]and the Java Applets in comment 14 > works fine, even when running them at the same time in different tabs, > running several applets in different tabs/windows, reloading pages, > closing tabs and windows etc... no problem. > > You have to cycle through the applets in the same tab (i.e. use only one tab and cycle through the applets, one after another, once the applet loads and is showing the animation).
OJI has been discontinued and Java now runs out-of-process, so this stuff has probably changed a lot. This bug has no info about current software versions, please file a new bug for new issues or reopen this one with current info, including a crash signature if it still happens and move it to a component outside of graveyard.
Status: NEW → RESOLVED
Closed: 13 years ago → 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.