Opened 5 months ago

Last modified 5 months ago

#15126 new bug

Input_server crashes on restart

Reported by: hitech Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Servers/input_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64

Description

While developing an input_server add-on, I had to restart the server quite a few times, with "input_server -q" from CLI. Once in every three restarts I was thrown into KDL, with the report attached.

This behavior was observed at least from June 13, 2019, and is persistent as of rev 53209. My platform is x64, I have no idea if this behavior can be reproduced on x86, therefore marking the platform as x64 only.

If I "continued", mouse was working, but keyboard was not.

A quick search for the functions in the report didn't return any bugs that look similar...

Attachments (1)

input_server-3617-debug-28-06-2019-01-36-16.report (15.2 KB ) - added by hitech 5 months ago.
Crash report of the input_server

Download all attachments as: .zip

Change History (4)

by hitech, 5 months ago

Crash report of the input_server

comment:1 by waddlesplash, 5 months ago

Appears to be a double-free assertion in the allocator. Can you retest this, running input_server with the guarded heap? (Dunno precisely how to do that in this scenario.)

comment:2 by hitech, 5 months ago

Possibly, blacklist input_server with adding into non-packaged FS the "input_server" symlink to a script that runs input_server with guarded heap? What is the way to run a program with the guarded heap? Will the suggested way work?

comment:3 by waddlesplash, 5 months ago

LD_PRELOAD=libroot_debug.so MALLOC_DEBUG=g [app] is the normal way.

Note: See TracTickets for help on using tickets.