Bug 577608

Summary: Eclipse exits when Switching Apps - GSlice: MemChecker: attempt to release block with invalid size
Product: [Eclipse Project] Platform Reporter: Heiko Selber <wadenwickel>
Component: RuntimeAssignee: platform-runtime-inbox <platform-runtime-inbox>
Status: NEW --- QA Contact:
Severity: major    
Priority: P3 CC: julien.henry
Version: 4.21   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Heiko Selber CLA 2021-12-03 03:30:33 EST 
On Ubuntu 20.04.3 LTS, Eclipse terminates immediately when I switch to another app using Alt-Tab.

This happens only the first time after logging into a Gnome session. When I restart Eclipse, it keeps running.

When I run Eclipse from a console it prints various errors before terminating, some involving GSlice.

When I run eclipse with

G_SLICE=debug-blocks eclipse

the last thing it prints before exiting is:

GSlice: MemChecker: attempt to release block with invalid size: 0x7f11d8ab5820 size=24 invalid-size=16

So it seems there is some memory corruption.
Comment 1 Julien HENRY CLA 2021-12-13 04:19:06 EST 
Same problem (I guess) here on Fedora 34 + plasmashell.

> plasmashell[14511]: ***MEMORY-ERROR***: Eclipse[14511]: GSlice: assertion failed: sinfo->n_allocated > 0

Only the first time I start Eclipse after starting KDE session. Then if I restart Eclipse it works fine.

Using JVM /usr/lib/jvm/java-11-openjdk-11.0.13.0.8-2.fc34.x86_64/bin/java
Comment 2 Heiko Selber CLA 2022-01-05 03:11:51 EST 
The problem persists with Eclipse 4.22.

By the way: if not run with 'G_SLICE=debug-blocks eclipse' Eclipse prints this error message on the console just before terminating:

***MEMORY-ERROR***: Eclipse[5374]: GSlice: assertion failed: sinfo->n_allocated > 0