Closed Bug 1194282 Opened 9 years ago Closed 9 years ago

Kibana 4.0.2 crashes Firefox 41.0b1

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
41 Branch
Platform:
x86_64
Windows 10
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox40 --- unaffected
firefox41 + verified
firefox42 + fixed
firefox43 + fixed

People

(Reporter: simon.trigona, Unassigned)

References

(
URL
)

Details

(Keywords: crash, regression)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150811185633

Steps to reproduce:

Open an instance of Kibana 4.0.2 (https://github.com/elastic/kibana) in Firefox 41.0b1.

Relevant Kibana issue: https://github.com/elastic/kibana/issues/4660
Relevant crash report: https://crash-stats.mozilla.com/report/index/d0054377-6d73-4f3a-b318-42ef62150813


Actual results:

Firefox crashes everytime.


Expected results:

Page loads successfully (as it did on Firefox 40 beta).
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Severity: normal → critical
Crash Signature: [@ CallGetter ]
Component: Untriaged → JavaScript Engine
Keywords: crash
Product: Firefox → Core
Thanks for the report! Rather than having to deploy our own Elastic search and kibana instances, would you have by luck any demo instances on which we could go and easily reproduce the bug, please?

Otherwise, if you have some time, do you mind using our mozregression tool [1] and help us bisect which changeset caused that particular bug, please?

[1] https://mozilla.github.io/mozregression/
Flags: needinfo?(simon.trigona)
I tried searching around online for an open demo of this Kibana version but was unsuccessful and am unable to expose my company's instance. I will take a look at the mozregression tool.
Flags: needinfo?(simon.trigona)
Ok.. spent a little time with the mozregression tool (fortunately it's easy to test) and here are the results:

Last good changeset: c0ab4a5c0acf
First bad changeset: e6f863562d50

Let me know if I can provide more details.
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c0ab4a5c0acf&tochange=e6f863562d50
Blocks: 1125624
Status: UNCONFIRMED → NEW
status-firefox40: --- → unaffected
status-firefox41: --- → affected
status-firefox42: --- → affected
status-firefox43: --- → affected
tracking-firefox41: --- → ?
tracking-firefox42: --- → ?
tracking-firefox43: --- → ?
Ever confirmed: true
Flags: needinfo?(jorendorff)
Keywords: regression
After a short search on Google, I found a public Kibana 4 demo crashing FF41+:
http://osgconnect.net/service/kibana/

CR FF41:
https://crash-stats.mozilla.com/report/index/b7605422-4247-42ed-9398-f6f8d2150814

CR FF43:
https://crash-stats.mozilla.com/report/index/9acd68d9-e60a-4205-aae3-96e4e2150814
URL: http://osgconnect.net/service/kibana/
Crash Signature: [@ CallGetter ] → [@ CallGetter ] [@ GetPropertyOperation ] [@ js::GetProperty(JSContext*, JS::Handle<T>, JS::Handle<T>, JS::MutableHandle<T>) ]
Fixed on trunk, probably one of the blockers need to be uplifted. Maybe bug 904886?
Oops, I was looking at the wrong list. Jandem pointed out to me bug 1189744, which fixed the issue (tested on the previous changeset: crash -- at the changeset, doesn't crash).

The regression has been fixed yesterday only, and should be on the next beta. The next beta should be available in a few days, so please let us know if that fixes your issue.
Flags: needinfo?(jorendorff) → needinfo?(simon.trigona)
Indeed, the latest Nightly doesn't crash anymore when loading http://osgconnect.net/service/kibana/ so it's probably a dupe of bug 1189744.
Tracking since this is a recent regression. Sounds like it may be fixed soon.
tracking-firefox42: ? → +
tracking-firefox43: ? → +
I can now confirm that 41.0b2 resolves the issue with Kibana.

Thanks team!
Flags: needinfo?(simon.trigona)
Thank you Simon for confirming the last beta fixes your issue.

Fixed by the uplift of bug 1189744 to the beta channel.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.