Closed Bug 556282 Opened 14 years ago Closed 14 years ago

Graphics Memory Screen Barf of Flash During Preloading (Core Animation Backend)

Categories

(Core Graveyard :: Plug-ins, defect)

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: perl.programmer, Assigned: BenWa)

References

()

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a4pre) Gecko/20100325 Minefield/3.7a4pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a4pre) Gecko/20100325 Minefield/3.7a4pre

I get a bunch of random video data from the graphics card when the page loads. Flash does absolutely no more loading until I move the mouse over the movie or click on it. At that point, everything loads properly and continues on.

Reproducible: Always

Steps to Reproduce:
1. Go to http://chromedshark.com/bugzilla/
2. Don't move mouse
Actual Results:  
Horribly garbled image barfed from graphics card.

Expected Results:  
Pretty flash preloader

I did this testing in safe mode, using the aforementioned build and Flash Player 10.1b3 debugger. The flash movie uses a custom preloader, so it must first load so many bytes from the flash file before it can actually start up the custom preloader. The horrible mess is showing up before the preloader finishes loading, and then interacting with the movie with the mouse triggers the preloader. The flash program should not work at all, because I just copied it off of our production servers so that it could be accessed without logging in, so don't worry if it stops with the preloader on the screen.
Attached image Example Screen Shot
Here's a screenshot I took of the screen barf happening.
I've seen this bug. I think that happens if flash does not draw right away even if it is loaded. Clearing the offscreen buffer should fix this.
Assignee: nobody → bgirard
Status: UNCONFIRMED → NEW
Ever confirmed: true
I think the problem is if we attach a CALayer to the CARenderer after NPAPI SetWindow has been called the layer is not initialized with the correct size until the plug-in is loaded. I have fixed this with out of process Core Animation so I will likely push this fix for in process at the same time hopefully next week.
Status: NEW → ASSIGNED
I investigated this issue further. We are calling |mInstance->SetWindow(mPluginWindow);| with:
(x=0, y=265, w=960, h=486) then right after,
(x=0, y=2413, w=0, h=0). These dimensions are incorrect.

Should the last SetWindow call not be happening or should I be calling SetWindow before doing a Core Animation draw?
This issue should be fixed when the patch for bug 559259 lands.
Depends on: 559259
Verified URL http://chromedshark.com/bugzilla/ for in/out-of-process Core Animation with:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a5pre)
Gecko/20100521 Minefield/3.7a5pre
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: