User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060524 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060524 Minefield/3.0a1 go too http://www.planetpdf.com/mainpage.asp?webpageid=1682 and firefox will crash Reproducible: Always Steps to Reproduce: 1.open http://www.planetpdf.com/mainpage.asp?webpageid=1682 in browser 2. 3. Actual Results: crash Expected Results: should not crash TB19110655Y TB19112728G

Works for me. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060523 Minefield/3.0a1 - Build ID: 2006052400

Confirmed on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060525 Minefield/3.0a1 ID:2006052505 [cairo] and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060521 Firefox/3.0a1 ID:2006052118 (debug) Attached is the stack trace (from debug build). Stack overflow.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060525 Minefield/3.0a1 ID:2006052508 [cairo] TB19112728G we'll have to see if this is a dupe or not if we get some feedback form the talkback server again

could this be the acrobat plugin that is crashing the browser? because on linux i just see the mssing plugin warning but no crash. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060525 Minefield/3.0a1

From Talkback-public.mozilla.org: Incident Not Found. DB error looking for Incident ID: 19112728

This looks like a regression in the adobe plugin. I've tried it with a few different trunk builds (even one from back in February) and they all crash. Even 1.5.0.3 does the same thing. But that was with version 7.0.7 of adobe reader installed. On another computer I still have 7.0.0 of the adobe reader program and it doesn't crash on that page with 1.5.0.3. Instead it puts up three alert boxes that each say "This operation is not allowed". And the page displays but without the examples. With the latest trunk nightly it does the same as 1.5.0.3 except only 2 alert boxes popup. About:plugins in firefox is misleading for the adobe plugin. On the two systems (with 7.0.7 and 7.0.0) about:plugins reports version 7.00. On yet another computer with adobe version 5.1 the first two examples work while the third example doesn't work. But no crash occurs. Is it possible to file bugs with adobe? And does anyone have intermediate versions of the plugin 7.0.1-7.0.6 to narrow down when this regressed?

(In reply to comment #6) > And does anyone have intermediate versions of the plugin 7.0.1-7.0.6 to narrow > down when this regressed? I've nppdf32.dll v7.0.5.172 and I crash.

I've found that version 7.0.3 of the plugin does not crash.

7.0.7 plugin does not crash with opera on same site

People, can you please stop spamming this bug with unnecessary WFMs and non-WFMs? --- Yes, we all know, that it is a confirmed crash. --- This may be a cause of an access violation, or invaild code that was compiled into the plugin DLL. --- TB19124014H is waiting to be processed in the TB server at this moment...

Incident ID: 19110655 Stack Signature nppdf32.dll + 0x626e (0x0fad626e) f6e0bb57 Product ID FirefoxTrunk Build ID 2006052505 Trigger Time 2006-05-25 10:09:40.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module nppdf32.dll + (0000626e) URL visited User Comments crash when loading page Since Last Crash 10900 sec Total Uptime 10900 sec Trigger Reason Stack overflow Source File, Line No. N/A Stack Trace nppdf32.dll + 0x626e (0x0fad626e) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f) USER32.dll + 0xe905 (0x77d4e905) nppdf32.dll + 0x6372 (0x0fad6372) USER32.dll + 0x8734 (0x77d48734) USER32.dll + 0x8816 (0x77d48816) USER32.dll + 0xc63f (0x77d4c63f)

timeless, I'm not sure why you changed Version to 1.8 branch if trunk suffers aswell

the version was unspecified and i had to pick a version when i moved to the right component. so i picked one. i'm often in a hurry and will only go back to verify things when i really think they matter. usually ff bugs are against branch, so i must have presumed that this was another branch build. it hardly matters. the bug's not our fault. we aren't the ones who managed to nest event loops with the os. we need someone who can speak for the acrobat plugin team, or who can find someone who does. msintov do you know a contact for them?

timeless did you add the DUPEME to this bug by accident or did you recall seeing another bug like this? I have found bug 325588 which is the same problem. And comment #4 from that bug: ------- Comment #4 From Jesse Ruderman 2006-03-21 16:39 PDT [reply] ------- The Adobe development team is aware of this bug.

(In reply to comment #14) > timeless did you add the DUPEME to this bug by accident or did you recall > seeing another bug like this? I have found bug 325588 which is the same > problem. Heck, maybe there should be a dependency with bug 325588, or somebody should dupe it.

Adding "Adobe Reader 7.0.x" in summary for ease of search.

polidobj@yahoo.com: i'm unlikely to add dupeme by accident. thanks for finding the right bug, in the future, you may resolve as duplicate :). *** This bug has been marked as a duplicate of 325588 ***