brightspot tests cause Assertion "((*cc != __null))" ("../core/NativeFunction.cpp":209)

NEW
Unassigned

Status

P1
normal
7 years ago
7 years ago

People

(Reporter: dschaffe, Unassigned)

Tracking

unspecified
Q1 12 - Brannan
x86
Mac OS X
Bug Flags:
flashplayer-qrb ?

Details

(Reporter)

Description

7 years ago
~550 brightspot tests out of 55,000 cause:
Assertion failed: "((*cc != __null))" ("../core/NativeFunction.cpp":209)

to reproduce:
1) mount p02filusr01.corp.adobe.com/Brightspot
2) get avmglue.abc, as3/swfs/j/Y/k/J/D/jYkJDyub0D5raWP0ZZ5LUXWv06GAFOPR9R5yWpL5As8=
3) get debug debugger shell, I reproduced with avmplus shell 2.1 debug-debugger build 6731:4dbf526976e9

$ avmshell_sd -Dverifyonly avmglue.abc as3/swfs/j/Y/k/J/D/jYkJDyub0D5raWP0ZZ5LUXWv06GAFOPR9R5yWpL5As8=
Assertion failed: "((*cc != __null))" ("../core/NativeFunction.cpp":209)
Trace/BPT trap

for now I will set the failures as expected failures.
(Reporter)

Updated

7 years ago
Flags: flashplayer-qrb?

Comment 1

7 years ago
are these new?  injection point?

if not new, are they related to bug 670804?

Comment 2

7 years ago
changeset: 6733:38193490f748
user:      Dan Schaffer <dschaffe@adobe.com>
summary:   bug 703262: mark brightspot failures as expected when triggering the assertion (r=me)

http://hg.mozilla.org/tamarin-redux/rev/38193490f748

Comment 3

7 years ago
marking P1 for Brannan on the assumption that assert = crash = better not ship.
Priority: -- → P1
Target Milestone: --- → Q1 12 - Brannan
dschaffe: is it possible for you to look into whether this is a dupe of Bug 670804 ?  (The idea was raised in comment 1.)
(In reply to Felix S Klock II from comment #4)
> dschaffe: is it possible for you to look into whether this is a dupe of Bug
> 670804 ?  (The idea was raised in comment 1.)

That request is probably unrealistic without more guidance/context.  I am thinking in particular of the fact that Brent and I have run into similar issues, and I spent some time investigating them; see
  Bug 670804, comment 19
  Bug 670804, comment 21
  Bug 670804, comment 23
You need to log in before you can comment on or make changes to this bug.