Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ref tests leak dom nodes #66

Closed
brson opened this issue Sep 7, 2012 · 2 comments
Closed

Ref tests leak dom nodes #66

brson opened this issue Sep 7, 2012 · 2 comments

Comments

@brson
Copy link
Contributor

@brson brson commented Sep 7, 2012

For some reason, running the ref tests (the png compositor) ends up leaking dom nodes, while the screen compositor does not. If I comment out the following lines in content_task it does not leak:

            let compartment = option::expect(self.compartment, ~"TODO error checking");                                                                        
            compartment.define_functions(debug_fns);                                                                                                           
            define_bindings(*compartment,                                                                                                                      
                            option::get(self.document),                                                                                                        
                            option::get(self.window));   
@Ms2ger
Copy link
Contributor

@Ms2ger Ms2ger commented Apr 27, 2014

@jdm, does this still happen?

ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Combine the functions so that servo#63, servo#66 ~ servo#69 can remove the file.

Still keep IndexedDB/support.js use vendor prefix.
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
…aine-IndexedDB

IndexedDB: BaptisteFontaine's tests from Test the Web Forward Paris (2012)
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
@nox
Copy link
Member

@nox nox commented Oct 10, 2015

This code doesn't even exist anymore, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.