Closed Bug 1427294 Opened 8 years ago Closed 8 years ago

Crash in mozalloc_abort | abort | libdbus-1.so.3.8.14@0x30514

Categories

(Core Graveyard :: X-remote, defect)

Unspecified
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1429021

People

(Reporter: mark.yen, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-401a819c-28cc-4d68-b896-c26ba0171228. ============================================================= Top 10 frames of crashing thread: 0 firefox mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33 1 firefox abort memory/mozalloc/mozalloc_abort.cpp:80 2 libdbus-1.so.3.8.14 libdbus-1.so.3.8.14@0x30514 3 libc-2.22.so libc-2.22.so@0x39e6b7 4 libdbus-1.so.3.8.14 libdbus-1.so.3.8.14@0x27150 5 libxul.so _fini 6 libdbus-1.so.3.8.14 libdbus-1.so.3.8.14@0x3176f 7 libdbus-1.so.3.8.14 libdbus-1.so.3.8.14@0x3154f 8 libdbus-1.so.3.8.14 libdbus-1.so.3.8.14@0x31574 9 ld-2.22.so ld-2.22.so@0xe0c6 ... 14 libxul.so nsDBusRemoteService::Startup toolkit/components/remote/nsDBusRemoteService.cpp:186 ============================================================= Build 20171228100111 (latest mozilla-central nightly), after bug 1418985 and bug 1420124 have landed. Steps to reproduce: 1. Close any existing Firefox instances 2. Launch Firefox (I used `./firefox -profile /some/empty/directory` to not clobber my profile); note that `-no-remote` or equivalent must not be in effect Expected results: New Firefox window (with some first run stuff) Actual results: Crash reporter. Additional Details: I go the following output on the console: process 30901: arguments to dbus_bus_request_name() were incorrect, assertion "_dbus_check_is_valid_bus_name (name)" failed in file dbus-bus.c line 1122. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Redirecting call to abort() to mozalloc_abort ExceptionHandler::GenerateDump cloned child 30964 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
I usually ask Martin about things like this :)
Flags: needinfo?(stransky)
It's a dupe of Bug 1429021 - when -profile param is given the profile name is empty.
Flags: needinfo?(stransky)
Thanks, Martin!
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.