forked from enlightenment/efl
eo: lower from CRI to ERR
Summary: unreffing too often is not good. However, its definitly not a critical error. Most of the wikipedia articles (*) that are speaking about ciritcal or fatal errors are highlighting that no reasonable recovery can be done. In our case a recovery is not even needed, due to our pointer safety we dont need to recover anything since the refcounting safed us from doing something stupid. ref T6987. Depends on D6384 Reviewers: zmike, segfaultxavi, devilhorns Reviewed By: zmike Subscribers: cedric, #committers Tags: #efl Maniphest Tasks: T6987 Differential Revision: https://phab.enlightenment.org/D6385
This commit is contained in:
parent
28aed68e7f
commit
4378d6feb9
|
@ -1923,7 +1923,7 @@ efl_unref(const Eo *obj_id)
|
||||||
{
|
{
|
||||||
if (obj->user_refcount < 0)
|
if (obj->user_refcount < 0)
|
||||||
{
|
{
|
||||||
CRI("Obj:%s@%p. User refcount (%d) < 0. Too many unrefs.",
|
ERR("Obj:%s@%p. User refcount (%d) < 0. Too many unrefs.",
|
||||||
obj->klass->desc->name, obj_id, obj->user_refcount);
|
obj->klass->desc->name, obj_id, obj->user_refcount);
|
||||||
_eo_log_obj_report((Eo_Id)obj_id, EINA_LOG_LEVEL_ERR, __FUNCTION__, __FILE__, __LINE__);
|
_eo_log_obj_report((Eo_Id)obj_id, EINA_LOG_LEVEL_ERR, __FUNCTION__, __FILE__, __LINE__);
|
||||||
EO_OBJ_DONE(obj_id);
|
EO_OBJ_DONE(obj_id);
|
||||||
|
|
Loading…
Reference in New Issue