284840 - clicking on [close] button in flash file crashes [@ ntdll.dll ] with sequence NPN_Invoke, NPP_Shutdown, NPN_Invoke

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[Canh]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

the original site was, "http://en.mysprite.com", I just chopped up the original
source code until the error was still reproduceable; the best I could, anyways

Reproducible: Always

Steps to Reproduce:
1. go to, http://www3.telus.net/canh/crashme.htm
2. wait until the [close] button appears then click on it

Actual Results:  
error, bugzilla

Expected Results:  
the popup should've closed properly as it does in IE

about:buildconfig

Build platform
target
i686-pc-cygwin

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE)

Configure arguments
--disable-ldap --disable-mailnews
--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth
--enable-crypto --disable-composer --enable-single-profile
--disable-profilesharing --enable-optimize --disable-debug --disable-tests
--enable-static --disable-shared --enable-official-branding

Comment 1

[Nickolay_Ponomarev]

Do you have a talkback id for this crash?

Comment 2

[Canh]

No, unfortunately I don't. Talkback did pop up and I did send the report,
though. I can't remember if I reformatted before or after that error; perhaps,
after because when I open up Talkback, it doesn't show me that report. I was
prompt the setup wizard.

Comment 3

[Nickolay_Ponomarev]

Well, in comment 0 you hint that the problem was reproducible for you with that
page. If it is still the case, please send another report and post its ID here.

Comment 4

[Canh]

Incident ID : TB4484094E

Also, the details capture can be found at, http://www3.telus.net/vinkev/details.txt

Comment 5

[Nickolay_Ponomarev]

heh, talkback-public is down and the link you're posted is 404.

Comment 6

[Canh]

The forces are conspiring against us. I dart my eyes as I'm typing. Anyways I
didn't bother to confirm that last link, error on my part. Apparently I can
download it and view it through ftp but I can't access it through http too. I
tried reuploading it and renaming it to a .htm extension, no luck. I uploaded it
on Geocities, though. Good ol' Geocities, link's at,
http://geocities.com/sslvl8318/details.txt

And this time I verified it's uploaded. As for uh, talkback-public, I realy
can't help you there, nor do I realy know what it is for that matter.

Comment 7

[timeless]

the details are useless, talkback-public is an interface to a server which holds
the symbols for the talkback enabled builds that you run, when you crash, the
talkback client sends the details you saw to the server which can pair them up
with the symbols to give us a useful stack trace. without the symbols on the
server the details are noise :(.

Comment 8

[Canh]

Ahh. Arcane stuff; symbols and sorcery.

Apparrently the webspace was working fine, I merely confused the username, it
should've been /canh/ instead of /vinkev/.

I find it annoying how this is  basically a board yet you can't modify your
threads; ridiculous, I say. Or perhaps you can and I'm missing something? care
to shed some more light? And are all those emails to all those people
neccessary? I feel I'm spamming, can't I modify who gets what? like this comment
which realy doesn't need to be sent to all those people.

Comment 9

[timeless]

people can choose not to get mail. if they choose not to choose not to get mail,
that's their choice. the bug tracking system is not generally designed so that
people can choose to hide their actions from others (with some exceptions for
security bugs and similar confidentiality issues). in some cases you can send a
private message to the individual commenter, but it wouldn't work for the
account listed for me, so you're stuck. it's not a big deal, there's lots of
noise here and we're used to it.

Comment 10

[Adam Hauner]

TB4484094E:
ntdll.dll + 0x18fea (0x7c918fea)
ntdll.dll + 0x104b (0x7c90104b)
NPSWF32.dll + 0x5dec5 (0x0477dec5)
NPSWF32.dll + 0x52397 (0x04772397)
NPSWF32.dll + 0x4b304 (0x0476b304)
NPSWF32.dll + 0x4b6ac (0x0476b6ac)
NPSWF32.dll + 0x44ed6 (0x04764ed6)
NPSWF32.dll + 0x4583a (0x0476583a)
NPSWF32.dll + 0x5f6c3 (0x0477f6c3)
NPSWF32.dll + 0x5d52e (0x0477d52e)
USER32.dll + 0x8709 (0x77d48709)
USER32.dll + 0x87eb (0x77d487eb)
USER32.dll + 0xc00e (0x77d4c00e)
USER32.dll + 0xe366 (0x77d4e366)
PluginWndProc 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/modules/plugin/base/src/nsPluginNativeWindowWin.cpp,
line 266]
USER32.dll + 0x8709 (0x77d48709)
USER32.dll + 0x87eb (0x77d487eb)
USER32.dll + 0x89a5 (0x77d489a5)
USER32.dll + 0x89e8 (0x77d489e8)
nsAppShell::Run 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/widget/src/windows/nsAppShell.cpp,
line 159]
nsAppShellService::Run 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 495]
main 
[d:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.0_Depend/mozilla/browser/app/nsBrowserApp.cpp,
line 58]
kernel32.dll + 0x16d4f (0x7c816d4f)

Comment 11

[Canh]

Still a problem in v1.0.4. TB5868687M. Reproduce is someone and update status to
confirmed; click on the [close] button at the top right-hand corner at the
following link, http://www3.telus.net/vinkev/crashme.htm.

Comment 12

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 13

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 14

[Canh]

This bug is unfortunately still a problem in FF 1.07. Talkback incident ID, TB10990327Y.

Comment 15

[timeless]

i'm sorry for gerv's rude message. in order to avoid dealing with it again, i'm going to uselessly confirm this bug.

[e-mail]: could you please investigate it?

Comment 16

[Michelle Sintov]

I've investigated this crash and can confirm that this is a Flash Player bug. We will investigate. Thanks so much for reporting this.

Comment 17

[Michelle Sintov]

I've investigated this further and think this is a browser bug, not a Flash Player bug.

Here's what is happening:
1. While processing a Windows timer callback, the plug-in calls NPN_Invoke, which blocks.
2. The browser calls NPP_Shutdown on the plug-in on the same stack that the plug-in is calling NPN_Invoke on. NPP_Shutdown completes.
3. NPN_Invoke returns and the plug-in continues processing the Windows timer callback.

Note that I'm UTR in Firefox 1.5 RC3.

Comment 18

[Martijn Wargers (dead)]

The url is 404, reporter could you put back the page?

Comment 19

[Canh]

Sorry, due to long inactivity I did some spring cleaning and deleted the file from my webspace. My fault, I should've added as an attachment, or just kept it since I didn't actually verify with the latest build if issue was resolved/unresolved.

Comment 20

[Wayne Mery (:wsmwk)]

without testcase, resolving incomplete