Open Bug 2015474 Opened 9 months ago Updated 4 months ago

[KDE] Crash in [@ mozilla::widget::WlLogHandler_InvalidDisplayObject]

Categories

(Core :: Widget: Gtk, defect)

defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

3.13 MB, application/octet-stream
Details

Crash report: https://crash-stats.mozilla.org/report/index/54bcb926-c43b-4045-8e10-859770260207

MOZ_CRASH Reason:

(kde) wl_display#1: error 0: invalid object 80141
 Proxy: WP:E WP:CA WP:CPCA

Top 10 frames:

0  libxul.so  MOZ_CrashSequence(void*, long)  mfbt/Assertions.h:237
0  libxul.so  MOZ_Crash(char const*, int, char const*)  mfbt/Assertions.h:375
0  libxul.so  mozilla::widget::WlLogHandler_InvalidDisplayObject(char const*)  widget/gtk/nsWaylandDisplay.cpp:933
1  libxul.so  mozilla::widget::WlLogHandler(char const*, __va_list_tag*)  widget/gtk/nsWaylandDisplay.cpp:1020
2  libwayland-client.so.0  libwayland-client.so.0@0x3401
3  libwayland-client.so.0  libwayland-client.so.0@0xab53
4  libffi.so.8  libffi.so.8@0x958f
5  libffi.so.8  libffi.so.8@0x4a5c
6  libwayland-client.so.0  libwayland-client.so.0@0x3838
7  libwayland-client.so.0  libwayland-client.so.0@0x35a0

There's only one crash comment under this signature but it may be useful:

Switching virtual desktop with Wayland+HDR enabled

'invalid object 80141' we may reference something already released but not sure what's that.

I experience this bug a few times per day, also while switching KDE desktops. Wayland ON+HDR OFF. It also manifests as mozilla::widget::WlLogHandler.

Severity: -- → S3

Hi, is there any additional info I can provide to help debug this?

(In reply to tchatow from comment #3)

Hi, is there any additional info I can provide to help debug this?

Yes. please run on terminal with WAYLAND_DEBUG=1 MOZ_LOG="WidgetScreen:5" env variables and attach the log here (when it crashes). For instance as:

WAYLAND_DEBUG=1 MOZ_LOG="WidgetScreen:5" firefox > log.txt 2>&1

and attach log.txt here.
Thanks.

Flags: needinfo?(tchatow)

I think we have similar one already reported. related to monitor plug/unplug.

Blocks: wayland

I recently updated many of the fedora packages (firefox still on 149.0.2), and since then have not observed any invalid object crashes. I did get one (kde) wl_display#1: error 1: invalid arguments for wl_display#1.sync.

Flags: needinfo?(tchatow)
Attached file log2.txt.tail.zst —

Display log associated with https://crash-stats.mozilla.org/report/index/7685487c-859d-467f-bcd0-0af9b0260518

I took just the end of the log because it was many GB.

Thanks. The log doesn't make much sense to me as it looks like

[1848053.852] {Default Queue}  -> zwp_linux_dmabuf_v1#48.create_params(new id zwp_linux_buffer_params_v1#310812)
[1848053.853] {Default Queue}  -> zwp_linux_buffer_params_v1#310812.add(fd 768, 0, 0, 4096, 33554432, 682016516)
[1848053.859] {Default Queue}  -> zwp_linux_buffer_params_v1#310812.add(fd 452, 1, 2097152, 1024, 33554432, 682016516)
[1848053.861] {Default Queue}  -> zwp_linux_buffer_params_v1#310812.create_immed(new id wl_buffer#310813, 1024, 512, 875713089, 0)
[1848053.863] {Default Queue}  -> zwp_linux_buffer_params_v1#310812.destroy()
[...]
[1848084.061] {Display Queue} wl_display#1.delete_id(229276)
[1848084.062] {Display Queue} wl_display#1.delete_id(231411)
[1848084.063] {Display Queue} wl_display#1.error(wl_display#1, 0, "invalid object 310812")
[GFX1-]: (kde) Wayland protocol error: wl_display#1: error 0: invalid object 310812 

This one looks like a KDE bug? Wrong tracking of the objects or so? I see bunch of delete_id calls so perhaps this is another (failed) one?

Vlad, any idea here?
Thanks.

Flags: needinfo?(vlad.zahorodnii)
Blocks: wayland-kde
No longer blocks: wayland
Summary: Crash in [@ mozilla::widget::WlLogHandler_InvalidDisplayObject] → [KDE] Crash in [@ mozilla::widget::WlLogHandler_InvalidDisplayObject]

Not sure to be frank. That protocol error will be posted if there is no wl_resource for the given id. But kwin should always create a params object or post the no memory error.

Flags: needinfo?(vlad.zahorodnii)

Thanks, added.

Crash Signature: [@ mozilla::widget::WlLogHandler_InvalidDisplayObject] → [@ mozilla::widget::WlLogHandler_InvalidDisplayObject] [@ <name omitted> | mozilla::widget::WlLogHandler_InvalidDisplayObject]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: