Opened 9 months ago

Closed 8 months ago

#16791 closed defect (limitation)

Windows Subsystem for Linux crash at startup: malloc corruption

Reported by: jobichenc@… Owned by: Greg Couch
Priority: normal Milestone:
Component: Platform Version:
Keywords: Cc: Tom Goddard, Zach Pearson
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

 Hi Eric,I was trying to install Chimerax in my DELL laptop using the WSL option.ucsf-chimerax_1.9ubuntu22.04_amd64.debChimerax crashes immediately upon opening and the bug report says Fatal Python error.I am unable to add any details into the bug report or submit the report.I ran with the option debug and attached the results in the attached file.Is there any known issues with installing the deb file? Can you please help.WIndows 11 with WSL _Dell latitude 5440 with 13th Gen Intel I7 processor.Thank you.Jobichen

chimerabug.txt

Attachments (1)

chimerabug.txt (111.7 KB ) - added by jobichenc@… 9 months ago.
Added by email2trac

Download all attachments as: .zip

Change History (3)

by jobichenc@…, 9 months ago

Attachment: chimerabug.txt added

Added by email2trac

comment:1 by pett, 9 months ago

Cc: Tom Goddard Zach Pearson added
Component: UnassignedPlatform
Owner: set to Greg Couch
Platform: all
Project: ChimeraX
Status: newassigned
Summary: Bug reportWindows Subsystem for Linux crash at startup: malloc corruption

Reported by Jobichen

comment:2 by Greg Couch, 8 months ago

Resolution: limitation
Status: assignedclosed

Sorry, WSL is not supported. If it works, great, if not, then that is the way things are. The exception to that is if the bug is reproducible on a supported Linux system. This one does not appear to be reproducible.

That said, we expect that it will work someday. It probably depends on bug fixes from Microsoft for WSL, and bug fixes for the Qt user interface toolkit that ChimeraX uses. There is also a chance that the bug would be fixed by using a different distribution of Linux than Ubuntu 22.04 for WSL.

To figure out where the bug is from a ChimeraX perspective, run ChimeraX under the gdb debugger. And then get a backtrace when it dies. So install the gdb package, then, in a terminal windows, "gdb /usr/bin/chimerax". Then at the "(gdb)" prompt, type "run". After that do whatever you did to make it crash. And when you see the gdb prompt again, give the "bt" command to print out a backtrace. Then copy and paste the backtrace into this ticket.

There might be an associated event in the Windows Event Viewer that would give you more information. So look there after the crash too.

Good luck debugging!

Note: See TracTickets for help on using tickets.