Bug 657622
| Summary: | [abrt] gnome-panel-2.30.2-5.el6: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Yogesh <ychavan> |
| Component: | libsoup | Assignee: | Dan Winship <danw> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.0 | CC: | case-diagnostics, jkoten, jwest, rdassen, rstrode, syeghiay, tpelka, vgaikwad |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 08:24:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 662543, 727267, 747123, 756082, 782183, 840699 | ||
|
Description
Yogesh
2010-11-26 20:40:08 UTC
Created attachment 463139 [details]
core dump
Created attachment 463140 [details]
sosreport
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. This request has been proposed for the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. I spent a little time today trying to figure out what's going on here. This doesn't look like a problem in the clock code but a problem in libsoup. I believe the trace in comment 0 is missing a frame between frame 0 and 1 thanks to compiler optimizations. I haven't tried yet to reproduce, but from code inspection that frame is probably something like: #0.5 got_connection (conn=0x26bdf10, status=200, session=0x2679680):299 which is the last line in the function and it calls do_idle_run_queue. If that guess is right, then the only way we could be here is from this code in run_queue: ... if (soup_connection_get_state (conn) == SOUP_CONNECTION_NEW) { soup_connection_connect_async (conn, got_connection, session); ... connect_async doesn't call got_connection until a GSource called watch_src setup by the soup_socket_connect_async function is ready. That source may be an io channel waiting for the socket being used to be ready or an idle source if the socket is already ready. If priv is NULL when do_idle_run_queue is called, as indicated in this bug report, then that means that session is probably freed memory. One possible way that session could be freed is from the weather_info_free call in libgweather, which unrefs the session object. Before doing this it calls soup_session_abort, though, which calls soup_session_cancel_message on whatever pending message lead to soup_connection_connect_async getting called. cancel_message makes sure some input sources are removed, but the watch_src source mentioned earlier isn't one of them. The async_cancel function seems to do the right thing, but it's only called by cancellables objects, and soup_connection_connect_async passes a NULL cancellable object to soup_socket_connect_async. Reassigning to libsoup. Fixed upstream in libsoup 2.32; the patch (http://git.gnome.org/browse/libsoup/commit/?id=a87e5833) applies more-or-less cleanly and doesn't break any of the existing libsoup tests; the additional test added by that patch can't be added to RHEL 6's libsoup because it depends on features that were added later. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. *** Bug 704349 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0313.html |