search

divyang4481 / firebreath

Automatically exported from code.google.com/p/firebreath
0 stars 0 forks source link

Force JSObjectPtr to be freed on correct thread #93

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create new thread from primary thread
2. Interact with JSObjectPtrs on the secondary thread
3. Watch assertion errors due to JSObjectPtr instances being freed on the wrong 
thread

Initially I was seeing this when dealing with callbacks.  Now I see it when 
interrogating the DOM from a secondary thread.

Original issue reported on code.google.com by nirvd...@gmail.com on 25 Oct 2010 at 2:35

GoogleCodeExporter commented 8 years ago 
Sorry I forgot about this.  We will do it for 1.3.  Should be a simple(ish) 
change.

Original comment by taxilian on 25 Oct 2010 at 2:39

GoogleCodeExporter commented 8 years ago

Original comment by taxilian on 25 Oct 2010 at 2:39

GoogleCodeExporter commented 8 years ago 
No problem. I wish I understood this a bit better because I'd just fix it 
myself. In the meanwhile, I eagerly await learning from your diff.

Original comment by nirvd...@gmail.com on 25 Oct 2010 at 2:41

GoogleCodeExporter commented 8 years ago 
Hopefully this is now fixed in both repos; please test and confirm

Original comment by taxilian on 25 Oct 2010 at 4:27