Control: severity -1 normal Control: reassign -1 enlightenment 0.23.1-4 Control: retitle -1 eo logs in .xsession-errors eat all disk space
On Tue, Feb 11, 2020 at 01:31:28PM +0300, sergio wrote: > Package: libecore1 > Version: 1.23.3-6 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > it's critical as it eats all disk space causing other programs fail and > lose data. I haven't seen this, so lowering the priority to normal. Let's try to figure out the trigger. > I don't know how to reproduce it. It happens after several days of > running enlightenment. (My desktop is always on.) > > At the beginning all works fine, and ~/.xsession-errors takes less than > 100Kb. But some time later I find it taking all free space (dozen > gigabytes in my case). How do you start enlightenment? Does your desktop suspend after inactivity? Do you leave any other EFL apps running? > It repeats the following two lines endlessly: > > ERR<32091>:eo ../src/lib/eo/eo.c:2192 efl_data_scope_get() Eo ID > 0x4000002d3617 is not a valid object. Current thread: main. This ID has > probably been deleted or this was never a valid object ID. (domain=0, > current_domain=0, local_domain=0, available_domains=[0 1 ], > generation=217, id=b4d, ref=1) > ERR<32091>:eo ../src/lib/eo/eo.c:1814 efl_isa() Eo ID 0x4000002d3617 is not a > valid object. Current thread: main. This ID has probably been deleted or this > was never a valid object ID. (domain=0, current_domain=0, local_domain=0, > available_domains=[0 1 ], generation=217, id=b4d, ref=1) Does this end if you restart enlightenemnt? (Main -> Enlightenment -> Restart) > With the previous version of E all worked fine, began to happen with the > update to 0.23.1-4 This bug was opened against libecore1, not enlightenment. I've reassigned. Ross