Closed Bug 1130734 Opened 8 years ago Closed 3 years ago

[meta] crash in mozalloc_abort | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError

Categories

(Core :: DOM: Content Processes, defect, P3)

Product:
Core
Component:
DOM: Content Processes
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
mozilla38
Tracking Flags:
Tracking Status
e10s + ---
firefox38 --- fixed

People

(Reporter: jimm, Unassigned)

References

(
URL
)

Details

(Keywords: crash, meta)

Crash Data

Attachments

(1 obsolete file)

See Also: → killhard-win
Depends on: 1130842
Attached patch patch (obsolete) — — Splinter Review 
Assignee: nobody → jmathies

    
  

        Attachment #8560999 -
        Flags: review?(wmccloskey)

    
    

    
  
Comment on attachment 8560999 [details] [diff] [review]
patch

woops, wrong bug.

        Attachment #8560999 -
        Attachment is obsolete: true

        Attachment #8560999 -
        Flags: review?(wmccloskey)

    
    

    
  
So far the reporting added in bug 1130842 isn't turning up much, first nine reports all match - 

MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'
MsgRouteError '(msgtype=0x840009,name=???) Route error: message sent to unknown actor ID'

    
    

    
  
(In reply to Jim Mathies [:jimm] from comment #1)
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=0c2f7434c325&tochange=34a66aaaca81

backed out bug 1127378 to see if it helps reduce this.

    
    

    
  
https://hg.mozilla.org/mozilla-central/rev/bca7d6e77486
Status: NEW → RESOLVED
Closed: 8 years ago

          status-firefox38:
          --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla38

    
  
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

    
    

    
  
Looks like that backout cleared these up.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → WORKSFORME

    
    

    
  
A few of these have shown up in the 2-10 build, possibly in smaller numbers. Have to wait and see.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

    
  

          tracking-e10s:
          ? → +
Keywords: meta

    
  
Depends on: 1132874

    
    

    
  
I just reproduced this on Nightly 18/03 whilst trying to reproduce bug 1130838

https://crash-stats.mozilla.com/report/index/78a3e9f6-41f2-459e-a194-8a49b2150319

I reproduced this by opening about 20 tabs with http://twitch.tv/directory and then closing them. It can take a while, so keep opening tabs and closing them until a content process crash occurs.

    
  
Summary: crash in mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*) → [meta] crash in mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)

    
    

    
  
Is it really fixed? I still see SendGetCookieString in the report.
Flags: needinfo?(jmathies)

    
  
Flags: needinfo?(jmathies)

    
  
Depends on: 1196799

    
  
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)] → [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)]
[@ mozalloc_abort | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError]

    
  
Summary: [meta] crash in mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*) → [meta] crash in mozalloc_abort | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError

    
    

    
  
Ran into this today on current FF Nightly 64-bit on Windows 10. https://crash-stats.mozilla.com/report/index/9ecaed8a-59a1-4906-80fd-acf4b2160426.

    
    

    
  
Adding a Mac signature which showed up recently in Nightly.
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)]
[@ mozalloc_abort | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError] → [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError(mozilla::ipc::HasResultCodes::Result, char const*)]
[@ mozalloc_abort | NS_DebugBreak | mozilla::dom::ContentChild::ProcessingError]
[@ mozalloc_abort | A…
Priority: -- → P2

    
    

    
  
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3

    
    

    
  
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

    
  
Assignee: jmathies → nobody

    
    

    
  
Closing because no crashes reported for 12 weeks.


Status: REOPENED → RESOLVED
Closed: 8 years ago → 3 years ago
Resolution: --- → WORKSFORME

          You need to log in
          before you can comment on or make changes to this bug.