[
https://issues.apache.org/jira/browse/THRIFT-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105827#comment-15105827
]
Chandler May commented on THRIFT-3567:
--------------------------------------
Empirically, after running make cross,(*)
grep GLib-GObject-CRITICAL test/log/*
prints those error messages and returns zero before the patch, whereas it
prints nothing and returns non-zero after the patch.
It seems a little out of the way, but it might be feasible to call
thrift_test_handler_test_insanity in isolation, then mimic what g_object_unref
would do to *_return and argument in the caller, unref-ing the entries one at a
time and checking G_IS_OBJECT before and after each one. If the implementation
is correct G_IS_OBJECT should fail immediately after the third unref (two
references in *_return and one for the caller).
(*) On a previous revision. After merging the last week's commits to master,
make cross runs the server feature tests instead of the cross-language tests.
Is this a mistake? In any case, the cross-language tests can be run via
test/test.py.
> GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)'
> failed
> ---------------------------------------------------------------------------------
>
> Key: THRIFT-3567
> URL: https://issues.apache.org/jira/browse/THRIFT-3567
> Project: Thrift
> Issue Type: Bug
> Components: C glib - Library
> Affects Versions: 0.9.3
> Reporter: Chandler May
>
> When running cross language tests with a c_glib server, I see g_object_unref
> assertion errors like these in the output logs:
> (lt-test_server:54378): GLib-GObject-CRITICAL **: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
