Yeah, we've used an updated set of plugins from a PPA for testing, didn't clean the cache and unity8 as crashing some 30% of the time on startup...
Disabling cache altogether when image writable would be good enough for our case. But then it would mean we're not testing the real thing and could miss issues that would only crop up once cache is enabled again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
