Le 13/11/2014 15:50, Tim Chien a écrit : > I was working bug 1098124 today, and I encounter a situation where > mozSettings simply breaks. For the entire phone for all apps. Probing > with breakpoints in the app I found that all DOMRequests for set() and > get() simply never resolves. Calling additional set() does not > reproduce any logcat. > > Not being able to come out with anything useful, I eventually reboot > the machine and bring it back to the normal state. > > The phone was running latest OTA version. > > This is pretty serious because in many apps Gaia rely on mozSettings > to return before doing anything else. Without working mozSettings we > will see issues like bug 1093121. > > Unfortunately this is not reproducible in any way. It might only > because I keep |APP=keyboard make install-gaia| which kills the app > from time to time during development. Since there is nothing useful > here I decide to e-mail instead of filing a bug. > > The other thing to ask is whether or not Gaia should defend against > this kind of API breakage. Should I wrap a setTimeout() around the > set() request and recover when it never returns? The code is going to > be ugly but at least the keyboard would show up.... >
I just want to note that there is an IndexedDB deadlock being worked on by Bent these days, see https://bugzilla.mozilla.org/show_bug.cgi?id=1078438. I don't know at all if this is related, but this could be. -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
