Firefox- Crash Report [@ js::AutoCompartment::AutoCompartment ]

VERIFIED FIXED in Firefox 10

Status

()

Core
JavaScript Engine
--
critical
VERIFIED FIXED
6 years ago
5 years ago

People

(Reporter: Yann Brelière, Assigned: mrbkap)

Tracking

({crash, topcrash})

Trunk
mozilla12
x86
All
crash, topcrash
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox9 affected, firefox10+ verified, firefox11- verified, firefox12- verified)

Details

(Whiteboard: [firebug-p1], crash signature, URL)

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0a1) Gecko/20110925 Firefox/9.0a1
Build ID: 20110925172321

Steps to reproduce:

On my session, in Firefox Nightly, every time I open https://www.gandi.net (or the dev or preprod website, or another page on the site), it crashes:


Actual results:

https://crash-stats.mozilla.com/report/index/bp-9c67f267-0a39-495f-8549-4e2282110926
https://crash-stats.mozilla.com/report/index/bp-a6e13aa8-7105-4d93-b51d-f1f272110926


Expected results:

In the nightly of the 21 or 22 of september, it worked fine.
(Reporter)

Updated

6 years ago
(Reporter)

Comment 1

6 years ago
The crash doesn't happen in another Nightly session or in private browsing mode. I have removed all my cookies for gandi.net and the crash still happens.
(Reporter)

Comment 2

6 years ago
It's a Firebug bug in fact: http://code.google.com/p/fbug/issues/detail?id=4861
If I deactivate Firebug, it doesn't crash anymore.
Crash Signature: [@ js::AutoCompartment::AutoCompartment ]

Comment 3

6 years ago
No idea what "Firefox-Trunk" is, but it also happens enough in Firefox Nightlies.
(Reporter)

Comment 4

6 years ago
Yes, it is Firefox Nightly. I guess it is called like that because the package in Ubuntu is firefox-trunk (this allows running firefox alongside): https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa.
Thanks for confirming.
I am marking as Firebug p1, since it's blocking Firebug on nightlies.

Could this problem be related to Bug 689101?
It looks like it appeared in the same regression range.

Honza
Whiteboard: [firebug-p1]

Comment 6

6 years ago
I guess comment 3 confirms the crash is valid.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 7

6 years ago
Great! I don't have the crash anymore, and Firebug works. I believe this is thanks to Bug 689101, so I don't know if this bug should be marked as a duplicate or as depending on Bug 689101.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
(In reply to Yann Brelière from comment #7)
> Great! I don't have the crash anymore, and Firebug works. I believe this is
> thanks to Bug 689101, so I don't know if this bug should be marked as a
> duplicate or as depending on Bug 689101.
Thanks for the update!

Honza
(In reply to Yann Brelière from comment #7)
> Great! I don't have the crash anymore, and Firebug works. I believe this is
> thanks to Bug 689101, so I don't know if this bug should be marked as a
> duplicate or as depending on Bug 689101.

I'll mark it as a duplicate. I'm glad it fixed this for you!
Resolution: WORKSFORME → DUPLICATE
Duplicate of bug: 689101

Comment 10

6 years ago
I'm not sure this is a duplicate of the other ticket, I'm still receiving crashes related to firefox nightlies and firebug javascript breakpoints.

I'll attach gdb output.

Comment 11

6 years ago
Created attachment 568449 [details]
GDB output

Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:10.0a1) Gecko/20111017 Firefox/10.0a1

firefox-trunk-10.0~a1~hg20111016r78825

https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa

Comment 12

6 years ago
Created attachment 568453 [details]
Correct GDB output

Of course I accidently overwrote the GDB output when it crashed in AutoCompartment, but still settingt breakpoints causes various crashes. I'll try to gather more, but most seem related to cyclecollector
Attachment #568449 - Attachment is obsolete: true
(Reporter)

Comment 13

6 years ago
I can confirm that this bug was in fact, not resolved.
I was thinking it was, because I could open Firebug and activate the console and the script panel without crashing.
But next time I start Nightly and open firebug on the tab where I activated the console, it crashes.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Yann, can you please attach your crash report?

Honza
(Reporter)

Comment 15

6 years ago
Do you know how I could do that? Firefox on ubuntu has removed crash-reporter (see bug 694950).

Comment 16

6 years ago
https://crash-stats.mozilla.com/report/index/bp-ce9c1d31-a1a5-4e4c-9401-51cdc2111028

Comment 17

6 years ago
May be related, where latest nightly crashes now when trying to reproduce:

https://crash-stats.mozilla.com/report/index/bp-18685c4b-176c-4706-80e7-80dff2111031
https://crash-stats.mozilla.com/report/index/bp-e76d6208-091a-46df-bb5e-05cf52111101
https://crash-stats.mozilla.com/report/index/bp-d060ea8f-fec1-4a8f-852e-e33f12111101

Comment 18

6 years ago
https://crash-stats.mozilla.com/report/index/bp-c25d8abc-3f5d-45ac-9199-a94982111108
I just had a similar crash.  Report - https://crash-stats.mozilla.com/report/index/bp-9ab3f2fc-d160-4843-b6fb-8dff02111124

Updated

6 years ago
Assignee: nobody → general
Severity: normal → critical
Component: General → JavaScript Engine
Keywords: crash
Product: Firefox → Core
QA Contact: general → general
Version: 9 Branch → Trunk

Comment 20

6 years ago
This is 100% reproducible for me - opening a specific page immediately takes down Firefox 9.0.1 for me, if Firebug is enabled.

https://crash-stats.mozilla.com/report/index/bp-6d51c202-96a6-4c0b-b3bf-8ec292120103
https://crash-stats.mozilla.com/report/index/bp-388cd0cf-2c20-4195-85a3-544352120103
https://crash-stats.mozilla.com/report/index/bp-4c18aef9-dce1-48db-8029-c158a2120103

Updated

6 years ago
Duplicate of this bug: 713251

Comment 22

6 years ago
Can you give the URL for that specific page?
(Assignee)

Comment 23

6 years ago
I bet this has to do with the value debugged being null.
Assignee: general → mrbkap
Blocks: 628758
(Assignee)

Comment 24

6 years ago
Created attachment 585410 [details] [diff] [review]
Proposed fix

I snuck in a warning fix since jsd is C and includes jsprvtd.h (via jsdbgapi.h, who knew). Looking further through this file shows that everywhere else null-checks the object if it uses JSVAL_IS_OBJECT.

I eagerly await the day that we can use JS::Value in jsd2.
Attachment #585410 - Flags: review?(luke)

Comment 25

6 years ago
(In reply to :aceman from comment #22)
> Can you give the URL for that specific page?

It's internal, sadly. I can put it up with the necessary licensing/copyright disclaimers that the responsible people require sometime tomorrow (it's end of business here in NL right now). Sorry!

My work machine is building 9.0.1 with  attachment 585410 [details] [diff] [review] right now. I'll test that ASAP tomorrow morning.

Comment 26

6 years ago
Comment on attachment 585410 [details] [diff] [review]
Proposed fix

Word.
Attachment #585410 - Flags: review?(luke) → review+
(Assignee)

Comment 27

6 years ago
Comment on attachment 585410 [details] [diff] [review]
Proposed fix

https://hg.mozilla.org/integration/mozilla-inbound/rev/5025534b9d88
Attachment #585410 - Flags: checkin+

Comment 28

6 years ago
Ah, I forgot to mention this here. I tested builds with/without the fix, and this fixes the problem for me.

Blake: what would be necessary for this to make Fx 10/11? It's a pretty annoying bug for people hitting it...
https://hg.mozilla.org/mozilla-central/rev/5025534b9d88
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla12

Updated

5 years ago
Duplicate of this bug: 701130

Comment 31

5 years ago
With combined signatures, it's #1 top crasher in 9.0.1 on Mac OS X with 25% of all Mac crashes, so I think it should be fixed in Aurora and Beta.
status-firefox10: --- → affected
status-firefox11: --- → affected
status-firefox12: --- → fixed
status-firefox9: --- → affected
tracking-firefox10: --- → ?
tracking-firefox11: --- → ?
Keywords: topcrash
OS: Linux → All
is bug 674568 related to this? having firebug enabled for my development process crashes firefox 9.0.1 constantly after testing form submits. is there anything i can do to hold me over until this patch lands?
Duplicate of this bug: 716426

Comment 34

5 years ago
Should it really wait to FF12 version to fix this bug ?

Many users appears to have this problem as reported on the crash stats :
https://crash-stats.mozilla.com/report/index/0b0851c4-5e1d-4ac4-92f2-6685c2120106 -> comments

This bug can be reached by the 3 000 000 people who use FireBug add-on each day.
https://addons.mozilla.org/fr/firefox/addon/firebug/statistics/?last=365

Isn't it a customer satisfaction rate ?

Regards,
Anael
Comment on attachment 585410 [details] [diff] [review]
Proposed fix

[Approval Request Comment]
Regression caused by (bug #): unknown

User impact if declined: Firebug (or another JSD client) crashes the browser in some circumstances

Testing completed (on m-c, etc.): commenters have tried it out in m-c

Risk to taking this patch (and alternatives if risky): minimal. It only matters when jsdval->val is null, and without the patch it's an immediate crash in that case. The new behavior is to pick a fallback object as the scope object, and it's the same fallback that is already used for numeric or other non-object values.
Attachment #585410 - Flags: approval-mozilla-beta?
Attachment #585410 - Flags: approval-mozilla-aurora?
(Assignee)

Comment 36

5 years ago
Comment on attachment 585410 [details] [diff] [review]
Proposed fix

[Approval Request Comment]
Regression caused by (bug #): bug 628758
User impact if declined: Firebug users will crash when debugging null values.
Testing completed (on m-c, etc.): Gijs has tested to make sure that this fixes the crash.
Risk to taking this patch (and alternatives if risky): This patch is as un-risky as it gets. It adds a null check and avoids crashing if the given value is null.

Note that the comment-fix part of this patch (js/src/jsprvtd.h) doesn't apply to aurora or beta and therefore won't be checked in. The comments being fixed don't exist on that branch.

Updated

5 years ago
tracking-firefox10: ? → +
tracking-firefox11: ? → +
Comment on attachment 585410 [details] [diff] [review]
Proposed fix

[Triage Comment]
Approving this top crasher with minimal risk (thanks for the background Steve and Blake) for both Aurora and Beta. Please land today to make the 4th beta. If this misses tomorrow's beta, we may have to reevaluate landing it for FF10.
Attachment #585410 - Flags: approval-mozilla-beta?
Attachment #585410 - Flags: approval-mozilla-beta+
Attachment #585410 - Flags: approval-mozilla-aurora?
Attachment #585410 - Flags: approval-mozilla-aurora+
(In reply to Blake Kaplan (:mrbkap) from comment #36)
> Comment on attachment 585410 [details] [diff] [review]
> Proposed fix
> 
> [Approval Request Comment]
> Regression caused by (bug #): bug 628758
> User impact if declined: Firebug users will crash when debugging null values.
> Testing completed (on m-c, etc.): Gijs has tested to make sure that this
> fixes the crash.
> Risk to taking this patch (and alternatives if risky): This patch is as
> un-risky as it gets. It adds a null check and avoids crashing if the given
> value is null.
> 
> Note that the comment-fix part of this patch (js/src/jsprvtd.h) doesn't
> apply to aurora or beta and therefore won't be checked in. The comments
> being fixed don't exist on that branch.
Is there any workaround for Firebug (on Firebug side) to avoid the crash?
Honza
(Assignee)

Comment 39

5 years ago
I don't think so. The bug is pretty low-level in JSD. The closest thing I can think of is to not debug objects that have null values as properties.
(Assignee)

Comment 40

5 years ago
https://hg.mozilla.org/releases/mozilla-aurora/rev/381825ff95c0
https://hg.mozilla.org/releases/mozilla-beta/rev/4b1ae47f1dd3
status-firefox10: affected → fixed
status-firefox11: affected → fixed

Comment 41

5 years ago
At first view : not for an "[@ js::AutoCompartment::AutoCompartment ]" bug.

But is it really a Firebug error ?
Really low level problem (which should be prevented by JS daemon : a typo on an extension should not result to a brutal crash of the whole Firefox !

Regards,
Anael
(In reply to Anael from comment #41)
> But is it really a Firebug error ?
> Really low level problem (which should be prevented by JS daemon : a typo on
> an extension should not result to a brutal crash of the whole Firefox !
Sure, agree.

I just wanted to do something for users running Firefox without the patch.

Honza

Updated

5 years ago
Duplicate of this bug: 716839
What is currently the target Firefox version for the patch?
I am getting quite a lot of questions about when this will be fixed.
Honza

Comment 45

5 years ago
It looks like it got into Firefox 10, 11 and 12 (per comment 40 and comment 29).

Comment 46

5 years ago
(In reply to Jan Honza Odvarko from comment #44)
> What is currently the target Firefox version for the patch?
Take a look at the tracking flags on the top right.
(In reply to Scoobidiver from comment #46)
> (In reply to Jan Honza Odvarko from comment #44)
> > What is currently the target Firefox version for the patch?
> Take a look at the tracking flags on the top right.
Ah, I see, thanks!
Honza

Updated

5 years ago
Duplicate of this bug: 716849
One of Fx user reproduce this issue even on Firefox 10 beta 4.
 Crashid here: https://crash-stats.mozilla.com/report/index/1dfcda37-46cb-4585-a164-ae5162120115
Status: RESOLVED → REOPENED
status-firefox10: fixed → affected
Resolution: FIXED → ---
Summary: Firefox-Trunk 9.0a1 Crash Report [@ js::AutoCompartment::AutoCompartment ] → Firefox- Crash Report [@ js::AutoCompartment::AutoCompartment ]

Comment 50

5 years ago
Created attachment 588827 [details]
A script that always triggers a crash for me

I attached a file that always triggers a crash for me. However, I don't know if it's the same crash this report is dealing with or not.

Updated

5 years ago
Attachment #588827 - Attachment description: A tiny bit of HTML that always tiggers a crash for me → A script that always triggers a crash for me
Attachment #588827 - Attachment mime type: text/plain → text/html
Duplicate of this bug: 718378

Comment 52

5 years ago
I just tried firefox 10 (beta) and it still crashes.

Comment 53

5 years ago
(Sorry for not doing this in one message.)

I just tried it in firefox 11 and it crashes there as well. I have adjusted the flags. (I can't seem to find firefox 12 or I would test there as well.)

See: https://crash-stats.mozilla.com/report/index/cfd73cd5-b41e-41cc-a5cd-791bf2120116

(And I hope the crash I am checking is the same as the crash in this bug - but I believe it is.)
status-firefox11: fixed → affected
status-firefox12: fixed → ---
(In reply to Ariel Shkedi from comment #53)
> (Sorry for not doing this in one message.)
> 
> I just tried it in firefox 11 and it crashes there as well. I have adjusted
> the flags. (I can't seem to find firefox 12 or I would test there as well.)
> 
> See:
> https://crash-stats.mozilla.com/report/index/cfd73cd5-b41e-41cc-a5cd-
> 791bf2120116
> 
> (And I hope the crash I am checking is the same as the crash in this bug -
> but I believe it is.)

Which version of Firebug are you using? Please try with 1.9.0, 1.10a1
Status: REOPENED → NEW
tracking-firefox12: --- → ?

Comment 55

5 years ago
(In reply to Swarnava Sengupta (:Swarnava) from comment #54)

> Which version of Firebug are you using? Please try with 1.9.0, 1.10a1

I used firebug 1.9.0 for all the tests.

I just tried firebug 1.10a1 and it still crashes. (But even if firebug works around it, that doesn't actually solve the crash.)
(Assignee)

Comment 56

5 years ago
Ariel, can you test with a trunk build? I believe your stack should be fixed by bug 712289 which hasn't yet received approval to land on Aurora or Beta.
Depends on: 712289

Comment 57

5 years ago
(In reply to Blake Kaplan (:mrbkap) from comment #56)
> Ariel, can you test with a trunk build? I believe your stack should be fixed
> by bug 712289 which hasn't yet received approval to land on Aurora or Beta.

I tried trunk (12) and the test I attached here no longer crashes it, unfortunately the original page I extracted the test from DOES cause a crash.

See: https://crash-stats.mozilla.com/report/index/cd8c097d-279a-456b-b853-624b92120116

Right now I am not able to try to find a small testcase that I can upload, but I will see if I can do so later.

Comment 58

5 years ago
(In reply to Blake Kaplan (:mrbkap) from comment #56)
> Ariel, can you test with a trunk build? I believe your stack should be fixed
> by bug 712289 which hasn't yet received approval to land on Aurora or Beta.
bug 712289 will land in 12.0a1/20120116.
Why its not land on 10 beta or 11 aurora? The supprt forum and army of awesome are covered with this issue, firefox 12 means we should wait 4month? :|

Comment 60

5 years ago
(In reply to Swarnava Sengupta (:Swarnava) from comment #59)
> Why its not land on 10 beta or 11 aurora?
The patch of this bug landed in Aurora and Beta.
For bug 712289 which its patch is recent, risks are evaluated by release drivers as there may be unknown side effects (high volume crashes in other places, for instance). For a null check risks are low, for many changed lines risks are high.

> The supprt forum and army of awesome are covered with this issue
It's about Firefox 9.0.1.

It's #63 top browser crasher in 10.0b4, #48 in 11.0a2 and #25 in 12.0a1.
On Mac OS X where it is a top crasher in 9.0.1, it's #19 top crasher in 10.0b4 and #54 in 11.0a2.

Comment 61

5 years ago
(In reply to Scoobidiver from comment #58)
> bug 712289 will land in 12.0a1/20120116.

I just tested 12.0a1/20120117 and it did not crash :)

What will it take to get the fix into 10? I was forced to downgrade back to 8 because I could not stand the constant crashes in 9.

Please tag this bug as a release blocker for 10.

Comment 62

5 years ago
(In reply to Ariel Shkedi from comment #61)
> I was forced to downgrade back to 8 because I could not stand the constant crashes in 9.

I'm using same "workaround" (but it is not so easy to get Firefox of version 8). Sometimes I also debug in Google Chrome/Chromium.

Comment 63

5 years ago
(In reply to Jan Pejša from comment #62)
> (In reply to Ariel Shkedi from comment #61)
> > I was forced to downgrade back to 8 because I could not stand the constant crashes in 9.
> 
> I'm using same "workaround" (but it is not so easy to get Firefox of version
> 8). Sometimes I also debug in Google Chrome/Chromium.

Same here, reproducable crashes mit firefox 9.0.1 and firebug 1.9.0 when debuggung extjs applications. This is with scientific linux 6.1. Downgraded to firefox 8.0.1 and disabled automatic updates. A download archive for older firefox releases would be helpful.

Comment 64

5 years ago
(In reply to Michael Hase from comment #63)
> A download archive for older firefox releases would be helpful.

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

And for really old stuff:

ftp://archive.mozilla.org/pub/mozilla.org/firefox/releases/

Generally, please don't fill up this bug report with just "Me too, please put this in Firefox 10" comments.

Instead of switching to an older version, consider switching to beta, aurora or development builds: you'll be able to spot issues like this sooner and help us fix them before they end up in the release build! :-)

(eg. http://www.mozilla.org/en-US/firefox/beta/, http://www.mozilla.org/en-US/firefox/aurora/ , http://nightly.mozilla.org/ )

Comment 65

5 years ago
(In reply to Gijs Kruitbosch from comment #64)
> (In reply to Michael Hase from comment #63)
> > A download archive for older firefox releases would be helpful.
> 
> http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

9.0.1 is oldest release, 8.0.1 is empty ;-)

> 
> And for really old stuff:
> 
> ftp://archive.mozilla.org/pub/mozilla.org/firefox/releases/

Great, thanks, this is what I needed.

> 
> Generally, please don't fill up this bug report with just "Me too, please
> put this in Firefox 10" comments.
> 
> Instead of switching to an older version, consider switching to beta, aurora
> or development builds: you'll be able to spot issues like this sooner and
> help us fix them before they end up in the release build! :-)
> 
> (eg. http://www.mozilla.org/en-US/firefox/beta/,
> http://www.mozilla.org/en-US/firefox/aurora/ , http://nightly.mozilla.org/ )

Ok, granted. I'll try to help a little bit, testpage is
http://dev.sencha.com/deploy/ext-4.0.7-gpl/examples/portal/portal.html

Results with different firefox versions and firebug 1.9.0 with active console and javascript debugger:

firefox 8.0.1: runs
firefox 9.0.1: crash
firefox 10.0b2: crash
firefox 11.0a2 (2012-01-17): runs
firefox 12.0a1 (2012-01-17): runs (firebug 1.10a1)

So my crash seems to be fixed in firefox 11 (aurora) and 12 (nightly).

Comment 66

5 years ago
(In reply to Ariel Shkedi from comment #61)
> What will it take to get the fix into 10?

According to comment #40, it has been taken for 10 (which is in the mozilla-beta repository right now) already, the first .

(In reply to Michael Hase from comment #65)
> firefox 10.0b2: crash

Please try the current beta, which is 10.0b4 (if you downloaded a previous beta, just use the update functionality [Help > About Firefox] and it will be updated to 10.0b4 automatically).


That said, please no "me too" comments, we already know that 9 crashes. 10 is headed for release on January 31, and current betas should have the fix. If you can verify that, you can help us make sure that we'll be good with the release on the 31st.

Comment 67

5 years ago
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #66)

> Please try the current beta, which is 10.0b4

Just tried it, and it still crashes.

https://crash-stats.mozilla.com/report/index/05d701b7-5ed6-4860-ac80-b909c2120118

> 10 is headed for release on January 31, and current betas should have the fix.
> If you can verify that, you can help us make sure that we'll be good with
> the release on the 31st.

But current betas do not have the fix, that's why all the worried comments. This bug needs to block 10 - if needs to be delayed, then delay it, but it can not be released like this.

Comment 68

5 years ago
(In reply to Ariel Shkedi from comment #67)
> (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #66)
> 
> > Please try the current beta, which is 10.0b4
> 
> Just tried it, and it still crashes.
> 
> https://crash-stats.mozilla.com/report/index/05d701b7-5ed6-4860-ac80-
> b909c2120118
> 
> > 10 is headed for release on January 31, and current betas should have the fix.
> > If you can verify that, you can help us make sure that we'll be good with
> > the release on the 31st.
> 
> But current betas do not have the fix, that's why all the worried comments.
> This bug needs to block 10 - if needs to be delayed, then delay it, but it
> can not be released like this.

The patch isn't in 10b4, it will be in b5, see http://hg.mozilla.org/releases/mozilla-beta/pushloghtml - b5 hasn't been cut yet, it seems, so you'll need to exercise some patience or make your own build off the mozilla-beta repo.

Anyway, even if that page would still crash with the same signature, repeating here that you would like this to block the release of Fx10 without additional information doesn't help. Instead, try to provide a testcase which still crashes with the patch applied, and good steps to reproduce. For now, please wait and check what happens in a Fx10 build *with* the fix.

Comment 69

5 years ago
(In reply to Gijs Kruitbosch from comment #68)
> The patch isn't in 10b4

How do you determine that? From all I'm seeing, 10b4 should have the fix. It was checked in on the 9th, b4 was being created on the 11th. And rev 4b1ae47f1dd3 is in https://hg.mozilla.org/releases/mozilla-beta/rev/FIREFOX_10_0b4_RELEASE from what I can tell.
But bp-05d701b7-5ed6-4860-ac80-b909c2120118 looks a lot like 10b4. So I'm really confused now.

Comment 70

5 years ago
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #69)
> (In reply to Gijs Kruitbosch from comment #68)
> > The patch isn't in 10b4
> 
> How do you determine that? From all I'm seeing, 10b4 should have the fix. It
> was checked in on the 9th, b4 was being created on the 11th. And rev
> 4b1ae47f1dd3 is in
> https://hg.mozilla.org/releases/mozilla-beta/rev/FIREFOX_10_0b4_RELEASE from
> what I can tell.
> But bp-05d701b7-5ed6-4860-ac80-b909c2120118 looks a lot like 10b4. So I'm
> really confused now.

There was an additional patch from bug 712289 (security-sensitive, I can't see it), see comment #56 and comment #58, which got landed later: http://hg.mozilla.org/releases/mozilla-beta/rev/59d8e5608ab7 . Sorry for the confusion I may have caused by just saying 'the' patch...

Comment 71

5 years ago
(In reply to Gijs Kruitbosch from comment #70)
> There was an additional patch from bug 712289 (security-sensitive, I can't
> see it), see comment #56 and comment #58, which got landed later:
> http://hg.mozilla.org/releases/mozilla-beta/rev/59d8e5608ab7 . Sorry for the
> confusion I may have caused by just saying 'the' patch...

Ah, forgot that. In that case, I hope people here will be testing 10b5, which is being created within the next days and should be out for the public on Friday, I hope.

Comment 72

5 years ago
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #71)
> (In reply to Gijs Kruitbosch from comment #70)
> > There was an additional patch from bug 712289 (security-sensitive, I can't
> > see it), see comment #56 and comment #58, which got landed later:
> > http://hg.mozilla.org/releases/mozilla-beta/rev/59d8e5608ab7 . Sorry for the
> > confusion I may have caused by just saying 'the' patch...
> 
> Ah, forgot that. In that case, I hope people here will be testing 10b5,
> which is being created within the next days and should be out for the public
> on Friday, I hope.

Thanks, I'll test 10b5 as soon as it's out. My tests in comment 65 were really done with 10b4, not 10b2. Just confused the version numbers.

Comment 73

5 years ago
I want to point that many of Firefox users want to use the browser. If using of the browser is not possible, they have strong reason to try (or to use) another browser. (Do you really want this?)

I think that reproducible crash should be fixed ASAP and not in next release (in Firefox 10?).

Motto:
- I do not want to test beta releases of the browser.
- I just want to use it.
- Final version MUST work.

(I apologize for unrelated comment - but I'm not satisfied with current solution)

Comment 74

5 years ago
(In reply to Jan Pejša from comment #73)
> I think that reproducible crash should be fixed ASAP and not in next release
> (in Firefox 10?).

Firefox 10 is ASAP. We probably wouldn't be able to deliver a well-tested update to many users in a week, and in less than two weeks we are releasing Firefox 10, which has the fix.

Comment 75

5 years ago
(In reply to Jan Pejša from comment #73)
> If using of the browser is not possible, they have strong reason to try (or to 
> use) another browser. 
How many new users will have Firebug installed (correlated at 96%)?
As Firebug is for Web developers, I think they can try 10.0b5 if 9.0.1 is unusable for them.

Comment 76

5 years ago
(In reply to Gijs Kruitbosch from comment #68)

> The patch isn't in 10b4, it will be in b5

I just tested 10b5 candidate dated Jan 18 and it did not crash :)

From: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/10.0b5-candidates/ if anyone else wants to test.

> Instead, try to provide a testcase which still crashes with the patch
> applied, and good steps to reproduce.

I tested both the testcase that I uploaded and http://dev.sencha.com/deploy/ext-4.0.7-gpl/examples/portal/portal.html and was not able to trigger a crash.

So all seems to be well.

Everyone else who is experiencing this: Please test the candidate as well if you can.

Comment 77

5 years ago
(In reply to Ariel Shkedi from comment #76)
> I just tested 10b5 candidate dated Jan 18 and it did not crash :)
> 
> From:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/10.0b5-candidates/ if
> anyone else wants to test.
> 
> > Instead, try to provide a testcase which still crashes with the patch
> > applied, and good steps to reproduce.
> 
> I tested both the testcase that I uploaded and
> http://dev.sencha.com/deploy/ext-4.0.7-gpl/examples/portal/portal.html and
> was not able to trigger a crash.
> 
> So all seems to be well.
> 
> Everyone else who is experiencing this: Please test the candidate as well if
> you can.

Tested the sencha examples and my own app which triggered the crash too. With 10.0b5-candidate Jan 18 and active firebug everything works well. Thanks for the great work.
Status: NEW → RESOLVED
Last Resolved: 6 years ago5 years ago
status-firefox10: affected → fixed
Resolution: --- → FIXED
status-firefox11: affected → ---
tracking-firefox11: + → ?

Comment 78

5 years ago
Verified in 10 Beta 5 in comment 76 and comment 77.
Verified in 11 Aurora and 12 in comment 65.
Status: RESOLVED → VERIFIED
status-firefox10: fixed → verified
status-firefox11: --- → verified
status-firefox12: --- → verified

Comment 79

5 years ago
(In reply to Ariel Shkedi from comment #76)
> I just tested 10b5 candidate dated Jan 18 and it did not crash :)

Yay, thanks. This will go out to beta users on Friday (unless QA finds problems) and to release users on Jan 31, so we are good. Anyone seeing this problem on 9 should either deactivate Firebug until 31st or just go and use Beta until then.

Updated

5 years ago
Duplicate of this bug: 720348

Comment 81

5 years ago
I've the same bug with Firefox 9.0.1 and 1.9.0 on Ubuntu 11.10

Comment 82

5 years ago
(In reply to KLEIN Stéphane from comment #81)
> I've the same bug with Firefox 9.0.1 and 1.9.0 on Ubuntu 11.10
It's fixed in Firefox 10.0b5.

Updated

5 years ago
tracking-firefox11: ? → -
tracking-firefox12: ? → -
You need to log in before you can comment on or make changes to this bug.