Closed
Bug 1313880
Opened 8 years ago
Closed 7 years ago
bug regularly crash
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bugzzzz, Unassigned)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
64.25 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160923185034 Steps to reproduce: nothing Actual results: a crash Expected results: nothing in particular. I was listning to mus sic on youtube
Thanks for writing a bug report but it's not very useful. We need some steps to reproduce the issue (URL e.g.) and a crash report you can find in about:crashes. https://developer.mozilla.org/en-US/docs/Mozilla/How_to_get_a_stacktrace_for_a_bug_report Without more details, this bug report will be closed as incomplete.
Flags: needinfo?(bugzzzz)
Keywords: crash
Comment 3•8 years ago
|
||
Hi bugzzz, I see from your User Agent that you use Firefox 45.0, is the ESR version or the release version? You can verify this in about Firefox by clicking the menu, then the question mark and choose "About Firefox" option. If is Firefox release version, can you please update the browser to the latest (49.0.2) version and see if this issue is still reproducible? You can download it from here: http://archive.mozilla.org/pub/firefox/releases/49.0.2/linux-x86_64/en-US/firefox-49.0.2.tar.bz2 If is still reproducible it will be helpful if you can provide a crash report like Loic suggested in comment 1.
I changed the version to 49.0.2 and have to wait for the bug to happen.
Comment 5•8 years ago
|
||
Hi bugzzzz, Is this still reproducible on your end using Firefox 49.0.2? If is still reproducible, can you please provide a crash report? However, Firefox 50.0 just landed and you can update your browser.
I had a crash on 50.0 yesterday and submitted it at : https://crash-stats.mozilla.com/report/index/e9ce4a67-4b14-433f-870e-8610a2161120#tab-modules See the attached file too
Comment 8•8 years ago
|
||
Hi bugzzz, Thanks for the crash report. I have tried to reproduce this issue on Ubuntu 15.04 but the browser didn't crashd. I have also installed the add-ons provided in "about:support" attached file in comment 7, but still the browser didn't crashed. It will be very helpful if you can find some steps to reproduce. Maybe a website you've visited when the browser crashed. However, based on your provided crash report I am assigning a component to this issue in order to involve the development team and get an opinion on this.
Crash Signature: [@ js::GCMarker::markAndScan<T> ]
Component: Untriaged → JavaScript: GC
Product: Firefox → Core
Comment 9•7 years ago
|
||
bp-e9ce4a67-4b14-433f-870e-8610a2161120 appears to be the only crash report submitted with the reporter's email address, so it's unclear what "regularly" means. Without more info this is incomplete
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(bugzzzz)
Resolution: --- → INCOMPLETE
Comment 10•7 years ago
|
||
I haven't had a crash since January. Now, two days in a row, I get two, and they both point here. https://crash-stats.mozilla.com/report/index/05f5f3bf-84cf-4991-a9ce-d9b922170326 https://crash-stats.mozilla.com/report/index/dd262143-c186-41e9-aa64-07b7a2170328 They both happened while perusing one feed, Towleroad.com's RSS feed: http://feeds.towleroad.com/towleroad/feed in The Old Reader: https://theoldreader.com/ I reload after the crash, and all seems to be fine. I'll make the comment that this feed always brings my speed way down, always causing Firefox to go 25% (quadcore CPU), and it has to be javascript that is making Firefox go nuts. Not that I know how to read the HTML generated, since it's all generated by theoldreader.com anyway. I don't know if this is enough to open this back up or not, but to make it repeatable, I'd create a new TOR account (a free one should work, just as well), add the feed, wait a few days to build some posts up, and then, just start scrolling down...
You need to log in
before you can comment on or make changes to this bug.
Description
•