1559532 - Crash in [@ mozalloc_abort | abort | libdbus-1.so.3.19.10@0xb78c]

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect, P3)

Description

[Asif Youssuff]

This bug is for crash report bp-afa72535-bd05-4953-b862-429ad0190614.

Top 10 frames of crashing thread:

0 firefox-bin mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 firefox-bin abort memory/mozalloc/mozalloc_abort.cpp:79
2 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0xb78c 
3 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x2d33f 
4 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x3ca5f 
5 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x3b5a7 
6 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x3bf3c 
7 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x2f863 
8 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x1bf15 
9 libdbus-1.so.3.19.10 libdbus-1.so.3.19.10@0x1d038 

I see this in the terminal:

dbus[3367]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../../dbus/dbus-message.c line 1366.
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 3376
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

This happens when I start developer edition on Ubuntu Eoan.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:overholt, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Andrew Overholt [:overholt]]

This feels difficult to take action on but let's try the allocator.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.