Bugzilla

(In reply to Rossen from comment #5)
> Hi Tom, trying the suggested setting makes no difference. 

Then, it seems it's not related to bug 1536796 at least at the moment.

> I am unable to run the debug build as I don't have full control over the device. What will the debug build do? I can look into how I can run it.

It would enable debug assertions and pipe warning messages that generated from our code to a console. If we have that, we can find where unexpected things start to happen.

For instance,  things like: ` [11455, Main Thread] WARNING: '!window', file /xxx/Work/mozilla-central/dom/cache/CacheStorage.cpp, line 571`.

(In reply to Rossen from comment #5)
> Hi Tom, trying the suggested setting makes no difference. 

Then, it seems it's not related to bug 1536796 at least at the moment.

> I am unable to run the debug build as I don't have full control over the device. What will the debug build do? I can look into how I can run it.

It would enable debug assertions and pipe warning messages that generated from our code to a console. If we have that, we can find where unexpected things start to happen.

For instance,  the log looks like: ` [11455, Main Thread] WARNING: '!window', file /xxx/Work/mozilla-central/dom/cache/CacheStorage.cpp, line 571`.

(In reply to Rossen from comment #5)
> Hi Tom, trying the suggested setting makes no difference. 

Then, it seems it's not related to bug 1536796 at least at the moment.

> I am unable to run the debug build as I don't have full control over the device. What will the debug build do? I can look into how I can run it.

It would enable debug assertions and pipe warning messages that generated from our code to a console. If we have that, we can find where unexpected things start to happen.

For instance,  the message looks like: ` [11455, Main Thread] WARNING: '!window', file /xxx/Work/mozilla-central/dom/cache/CacheStorage.cpp, line 571`. With this, we can know it happens on which line and thus figure out the issue quickly.

(In reply to Rossen from comment #5)
> Hi Tom, trying the suggested setting makes no difference. 

Then, it seems it's not related to bug 1536796 at least at the moment.

> I am unable to run the debug build as I don't have full control over the device. What will the debug build do? I can look into how I can run it.

It would enable debug assertions and pipe warning messages that generated from our code to a console. If we have that, we can find where unexpected things start to happen.

For instance,  the message looks like: ` [11455, Main Thread] WARNING: '!window', file /xxx/Work/mozilla-central/dom/cache/CacheStorage.cpp, line 571`. With this, we can know it happens on which line of code and thus figure out the issue quickly.