Closed Bug 775646 Opened 13 years ago Closed 13 years ago

[adbe 3294632] crash in F1989942690

Categories

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Product:
External Software Affecting Firefox Graveyard
Component:
Flash (Adobe)
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(firefox15+ verified)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox15 + verified

People

(Reporter: marcia, Unassigned)

References

Details

(Keywords: crash, reproducible, testcase, Whiteboard: [flash-11.3][fixed in Flash 11.3.300.268])

Crash Data

Attachments

(1 file)

AaronMT - about:support
2.71 KB, text/plain
Details
This bug was filed from the Socorro interface and is report bp-d5439020-fe0a-4f2e-be1a-e4c5d2120719 . ============================================================= This is a crash that is generated from Martijn's test case in Bug 763237. 1. Load https://bugzilla.mozilla.org/attachment.cgi?id=635741 2. Receive the attached crash report on some machines. Martijn, Juan and Aaron were able to reproduce this on their Win 7 machines but I have not been able to so far. If you can provide your machine information from about:support or from DxDiag that would likely help. Frame Module Signature Source 0 NPSWF32_11_3_300_265.dll F1989942690_____________________________________________________________________ F_280847721____________________________________________________:272 1 NPSWF32_11_3_300_265.dll F913258907____________________________ F_1900438979_________________________________________:22077 2 NPSWF32_11_3_300_265.dll F1546913566_____________________________________ F1157779535_________________________________________________________________________:4362 3 NPSWF32_11_3_300_265.dll F1187989989____________________________________________ F1157779535_________________________________________________________________________:346 4 user32.dll InternalCallWinProc 5 user32.dll UserCallWinProcCheckWow 6 user32.dll DispatchMessageWorker 7 user32.dll DispatchMessageW 8 FlashPlayerPlugin_11_3_300_265.exe F425467176_____________________________________________________ F_540393159_____________________________________________________________________:358 9 FlashPlayerPlugin_11_3_300_265.exe F849276792______________________________ F_540393159_____________________________________________________________________:199 10 FlashPlayerPlugin_11_3_300_265.exe F_1338064323______________________________________________ F1922230711____________________________________________________________________:80 11 FlashPlayerPlugin_11_3_300_265.exe F802476640______________________ F674807226__________________________________________________________________:453 12 FlashPlayerPlugin_11_3_300_265.exe F_138606341_____________ F674807226__________________________________________________________________:350 13 FlashPlayerPlugin_11_3_300_265.exe F1419126855_______________________________________________________________ F_1358850170___________________________________________________________________:399 14 FlashPlayerPlugin_11_3_300_265.exe WinMain F_1358850170___________________________________________________________________:552 15 FlashPlayerPlugin_11_3_300_265.exe __tmainCRTStartup f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c:263 16 kernel32.dll BaseThreadInitThunk 17 ntdll.dll __RtlUserThreadStart 18 ntdll.dll _RtlUserThreadStart
Does it happen with Flash 11.4 Beta 1 (http://labs.adobe.com/downloads/flashplayer11-4.html)?
See Also: → 763237
Keywords: testcase
Sal/Jeromie - this doesn't yet appear to be a high volume crasher, but we'd like to get it on your radar nonetheless since we're having some luck reproducing.
thank alex. we have it tracking internally in #3294632. it is in "to test" to reproduce and should move along once we do...
Summary: crash in F1989942690 → [adbe 3294632] crash in F1989942690
we can consistently reproduce in 11.3.300.265 but NOT in Cyril +3, 11.3.300.268/11.4. martijn_ would you mind to try 11.3.300.268 to see if that build resolves that particular crash? thanks...
Where can I download that build, I can't see it at http://fs/public/Adobe%20Flash%20Testing/
Sorry about that, fs should be updated now.
tracking-firefox15: ? → +
Keywords: reproducible
Whiteboard: [flash-11.3]
(In reply to smadayag from comment #5) > martijn_ would you mind to try 11.3.300.268 to see if that build resolves > that particular crash? thanks... Thanks, it seems to be fixed in that build, indeed.
Status: NEW → RESOLVED
Closed: 13 years ago
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
Resolution: --- → FIXED
Whiteboard: [flash-11.3] → [flash-11.3][fixed in Flash 11.3.300.268]
Version: 17 Branch → 11.x
Is there any way to determine that this crash signature didn't move?
(In reply to Alex Keybl [:akeybl] from comment #10) > Is there any way to determine that this crash signature didn't move? Pretty hard to do, esp. as the obfuscated symbols don't give us any hint if something else is in the same area. That said, we haven't seen any significant new .268-only crash signatures so far.
Let's leave this open till we're sure the signature hasn't moved (symbols are coming shortly, I believe).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Alex Keybl [:akeybl] from comment #12) > Let's leave this open till we're sure the signature hasn't moved (symbols > are coming shortly, I believe). Given comment #5, there seems to be good QA on this having been fixed, so I wonder why you're reopening as this basically makes this an unactionable report. Even public unobfuscated symbols like we have for our own stuff can usually not help us too much to make the determination if a signature moved, and even there it's usually better to close one bug and open another for the new signature.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #13) > Given comment #5, there seems to be good QA on this having been fixed, so I > wonder why you're reopening as this basically makes this an unactionable > report. Even public unobfuscated symbols like we have for our own stuff can > usually not help us too much to make the determination if a signature moved Ah - so this isn't a problem that can be solved by getting symbols from Adobe? If that's the case, we can set this to resolved again.
(In reply to Alex Keybl [:akeybl] from comment #14) > Ah - so this isn't a problem that can be solved by getting symbols from > Adobe? If that's the case, we can set this to resolved again. Yes, I don't think that symbols would actually help much in any case (I guess you mean unobfuscated symbol, as we have obfuscated ones already).
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Verified as fixed in Firefox 15.0 beta 4 with Flash 11,4,400,252.
status-firefox15: fixed → verified
I see that this crash is reproducible, but I don't see a set of steps that people are using.
Guess I missed the testcase in Comment 0 - I assume that is what Ioana used in Comment 16. (In reply to Marcia Knous [:marcia] from comment #17) > I see that this crash is reproducible, but I don't see a set of steps that > people are using.
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 11.x → unspecified
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: