summaryrefslogtreecommitdiff
path: root/src/lib/eo/eo.c
diff options
context:
space:
mode:
authorMarcel Hollerbach <mail@marcel-hollerbach.de>2018-06-25 06:50:31 -0400
committerMike Blumenkrantz <zmike@samsung.com>2018-06-25 06:50:31 -0400
commit4378d6feb9b62b11870d76c918fcbb7a95197fee (patch)
treeb841c0263ecffcb220a77bb267bd33e14c9794fb /src/lib/eo/eo.c
parent28aed68e7f30b8858b041213ea10bfa1054a6b40 (diff)
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
Diffstat (limited to 'src/lib/eo/eo.c')
-rw-r--r--src/lib/eo/eo.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/eo/eo.c b/src/lib/eo/eo.c
index 63cb2a2..f2ee051 100644
--- a/src/lib/eo/eo.c
+++ b/src/lib/eo/eo.c
@@ -1923,7 +1923,7 @@ efl_unref(const Eo *obj_id)
1923 { 1923 {
1924 if (obj->user_refcount < 0) 1924 if (obj->user_refcount < 0)
1925 { 1925 {
1926 CRI("Obj:%s@%p. User refcount (%d) < 0. Too many unrefs.", 1926 ERR("Obj:%s@%p. User refcount (%d) < 0. Too many unrefs.",
1927 obj->klass->desc->name, obj_id, obj->user_refcount); 1927 obj->klass->desc->name, obj_id, obj->user_refcount);
1928 _eo_log_obj_report((Eo_Id)obj_id, EINA_LOG_LEVEL_ERR, __FUNCTION__, __FILE__, __LINE__); 1928 _eo_log_obj_report((Eo_Id)obj_id, EINA_LOG_LEVEL_ERR, __FUNCTION__, __FILE__, __LINE__);
1929 EO_OBJ_DONE(obj_id); 1929 EO_OBJ_DONE(obj_id);