Closed Bug 1083353 Opened 10 years ago Closed 10 years ago

crash in AppendUTF16toUTF8(nsAString_internal const&, nsACString_internal&, mozilla::fallible_t const&)

Categories

(Core :: DOM: Workers, defect)

Product:
Core
Component:
DOM: Workers
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1083425
Tracking Flags:
Tracking Status
firefox36 --- affected

People

(Reporter: metasieben, Unassigned)

Details

(Keywords: topcrash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-81688ed8-afa6-4084-86e2-ff43e2141015.
=============================================================
Did you file this because it's a crash you experienced, or because it's a topcrash? Do you have steps to reproduce?
Component: XPCOM → Networking: WebSockets
Flags: needinfo?(mozilla)
It happened to me.

Sadly the STRs aren't very helpful(probably):
1) was watching a twitch.tv past-broadcast.
2) clicked on the twitch-logo to return to the start-page while video was playing.

Since there weren't any bugs on file with this SIG, but multiple releated crashes(200+ in 28days), i filed this bug.
Flags: needinfo?(mozilla)
I just hit this in nightly (Mac, 10/15) clicking on the Home button (in the page) on a HuffingtonPost.com article.

https://crash-stats.mozilla.com/report/index/9e107cf2-f2d5-4b8e-989f-8b07f2141015
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: Networking: WebSockets → DOM: Workers
Hit this myself when I clicked on one of the pagination buttons in a forum thread at roosterteeth.com.
I can't get a consistent STR, but it did happen thrice in 15 minutes for me.
https://crash-stats.mozilla.com/report/index/57013645-b9c5-45db-8dda-aedf62141016

effects windows 8.1 to it seems just had this crash "assuming its the same others can confirm for sure"
OS: Mac OS X → All
I had clicked a link to stackoverflow from the results page of a Bing search; immediate crash.

What I did:
1. Navigate to Bing.com
2. search `esprima example`
3. Click 1st smaller link under second result [0]
esprima - Javascript Object from External file, program ...Mar 10, 2014Resolved

Expected:
Page to load

Actual:
Immediate crash

[0] http://stackoverflow.com/questions/22290521/javascript-object-from-external-file-program
Hit this too, https://crash-stats.mozilla.com/report/index/5b7a16df-3a14-49f1-95ff-120642141017.

This happened while clicking links on news.ycombinator.com. Had just opened a New Yorker tab in the background and was in the process of opening another link in another tab.
BTW, this does appear to be the #4 topcrash in 36.0a1 right now.
I think other topcrashes in 36.0a1 may be related (#4, 5, and 9 currently) making this actually the #2 top crash for Nightly with 3035/20631 crashes in the last 7 days. 

- https://crash-stats.mozilla.com/report/list?product=Firefox&range_value=7&range_unit=days&date=2014-10-17&signature=nsAString_internal%3A%3AEndReading%28nsReadingIterator%3Cwchar_t%3E%26%29&version=Firefox%3A36.0a1#tab-sigsummary

- https://crash-stats.mozilla.com/report/list?product=Firefox&range_value=7&range_unit=days&date=2014-10-17&signature=AppendUTF16toUTF8%28nsAString_internal+const%26%2C+nsACString_internal%26%29&version=Firefox%3A36.0a1
Crash Signature: [@ AppendUTF16toUTF8(nsAString_internal const&, nsACString_internal&, mozilla::fallible_t const&)] → [@ AppendUTF16toUTF8(nsAString_internal const&, nsACString_internal&, mozilla::fallible_t const&)] [@ nsAString_internal::EndReading(nsReadingIterator<wchar_t>&) ]
status-firefox36: --- → affected
Keywords: topcrash
Three crashes pretty much in a row, same signature.

Mac 10.9.

http://store.workwhilewalking.com seems to trigger a crash for me quite reliably. Click around.
(In reply to Richard Newman [:rnewman] from comment #12)
> http://store.workwhilewalking.com seems to trigger a crash for me quite
> reliably. Click around.

If you sort the responses in the network tab by HTTP response code, you'll see an HTTP 101 Switching Protocols which is indeed the Websocket handshake.  It looks like if you navigate to another page quickly before the handshake is completed, you'll see this crash.

Maybe a better title for the bug is "Crash when navigating from page mid WebSocket handshake"?

Based on the stack trace, it looks like this issue is due to leaving the page before upgrading.

I'd describe the stack trace as:
When clicking a link, stop loading the page, cancel all pending network requests.  Get the name of each pending request (oops the name of one of the network requests related to websockets doesn't exist (was probably cleaned up elsewhere)!).
probly a dup of 1083425 ..
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.