Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1458498
| Summary: | [abrt] Crash under soup_socket_new() | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gwendal <ezwen-redhatbugzilla> | ||||||||||||||||||||||||||
| Component: | libsoup | Assignee: | Milan Crha <mcrha> | ||||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 27 | CC: | alexl, anass.1430, caillon+fedoraproject, danw, djasa, elleander86, fredoche, gnome-sig, joshua.rich, marco.preve, mbarnes, mcrha, me, mh7596, mrckndt, pjnodine, plroskin, rhughes, rstrode, sandmann, sppopuri, tamilarasan.r1, thomas.perrot, tpopela | ||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/b5dbc7f0b47164630fbea3bc6e94a148cdd14db8 | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:f0a2634324ece5ab1edb5fce8ae7172971a06fd9;VARIANT_ID=workstation; | ||||||||||||||||||||||||||||
| Fixed In Version: | libsoup-2.60.2-2.fc27 | Doc Type: | If docs needed, set a value | ||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2017-11-21 23:33:39 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: | |||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
Gwendal
2017-06-03 12:53:13 UTC
Created attachment 1284665 [details]
File: backtrace
Created attachment 1284666 [details]
File: cgroup
Created attachment 1284667 [details]
File: core_backtrace
Created attachment 1284668 [details]
File: cpuinfo
Created attachment 1284669 [details]
File: dso_list
Created attachment 1284670 [details]
File: environ
Created attachment 1284671 [details]
File: exploitable
Created attachment 1284672 [details]
File: limits
Created attachment 1284673 [details]
File: maps
Created attachment 1284674 [details]
File: open_fds
Created attachment 1284675 [details]
File: proc_pid_status
Created attachment 1284676 [details]
File: var_log_messages
Thanks for a bug report. I think this is a similar issue as yours bug #1446226, only this time in the calendar factory, not in the address book factory. I'm wondering how to debug this further, as you seem to be able to reproduce this often, while I do not face it myself here, neither I see any recent reports from other users about the same thing (which might not necessarily mean much, as used can have set up to not report issues to bugzilla by default; on the other hand, the FAF URL (above) shows only one occurrence for the past month). Hi! Unfortunately I have no idea why this is happening :(. There must be something very specific to my case, maybe due to something weird with the exchange server that I use for work. If you have any idea how I can give you more information to help you investigate, please do not hesitate. And if this bug does not get fixed, it's completely fine, as from my perspective this is simply an ABRT notification popping up once in a while. No big deal. Your environment is great, because it can reproduce the issue. Where the actual problem is is the question, it can be in any library, from evolution-ews to libsoup (I vaguely recall some libsoup issues not being fixed, but I do not have any exact pointers and my memory is poor) or even lower in the stack.
I usually try to catch such memory issues with valgrind. The downside of valgrind is that it significantly slows down the responses, due to all the memory checking. It also causes high CPU usage for the same reason.
The commands would be to run the background processes from a terminals:
a) open one terminal window and run there:
$ G_SLICE=always-malloc valgrind --num-callers=30 --trace-children=yes \
/usr/libexec/evolution-calendar-factory -w &>~/ecf.log
b) open another terminal window and run there:
$ G_SLICE=always-malloc valgrind --num-callers=30 --trace-children=yes \
/usr/libexec/evolution-addressbook-factory -w &>~/ecf.log
c) wait a bit, until the both processes settle their activity, which will
also mean that they are registered on the D-Bus and they replaced
those previously runnign background processes
d) kill running evolution-alarm-notify process, either with:
$ pkill evolution-alarm-notify
or get its process ID:
$ ps ax | grep evolution-al
and then stop it:
$ kill -TERM PID
e) run evolution and use it "as before" (quotes due to significantly slower
response from both calendars and address books)
Valgrind is able to avoid certain crashes and it notifies about them only. Thus even if you'd not receive any crash, the logs can still contain valuable information. If you can, please, try to use it for a day or so, but if it'll slow your work too much, then just stop the processes from a) and b) (by using Ctrl+C in the respective terminal window) and work as before.
The thing is that due to the memory checking the valgrind can avoid the issue only for the slowness, in case the issue depends on "proper timing". There are other possibilities, like using address sanitizer, but it requires special build of the packages, which is not practical.
(In reply to Milan Crha from comment #15) > /usr/libexec/evolution-calendar-factory -w &>~/ecf.log > ... > /usr/libexec/evolution-addressbook-factory -w &>~/ecf.log Oops, the calendar factory should use ecf.log, while the address book factory eaf.log, definitely not the same file. Copy&paste error on my side, I'm sorry about that. Similar problem has been detected: Trying to add recipients from address book. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2938x15 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2938/15 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/libexec/evolution-addressbook-factory-subprocess journald_cursor: s=fa3b7875031e412ab6834e77cb9d413b;i=8f06;b=3e19ab9711d54a55ad15bdf23a80ca8e;m=1e5f341e5;t=55533b85e5543;x=eb5a5292664e2e18 kernel: 4.11.11-300.fc26.x86_64 package: evolution-data-server-3.24.4-1.fc26 reason: evolution-addressbook-factory-subprocess killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 I'm moving this to libsoup, I saw a similar issue also with a CalDAV calendar backend, thus it's not evolution-ews specific, even it strikes there the most. I'm not able to reproduce it currently (I saw it few months back, but even then it was more like a bad luck than consistent reproducer). *** Bug 1488588 has been marked as a duplicate of this bug. *** *** Bug 1491196 has been marked as a duplicate of this bug. *** *** Bug 1493742 has been marked as a duplicate of this bug. *** *** Bug 1498981 has been marked as a duplicate of this bug. *** *** Bug 1505700 has been marked as a duplicate of this bug. *** *** Bug 1484940 has been marked as a duplicate of this bug. *** *** Bug 1459045 has been marked as a duplicate of this bug. *** While this happens most often in connection with evolution-data-server background processes, involving evolution-ews backend, the bug #1459045 is from gnome-software package and bug #1484940 from corebird package, which sort of confirms that the issue is somewhere in libsoup (eventually in other common part between these packages). An upstream bug report [1] contains a proposed fix. I'll probably create an update in Fedora, once the upstream fix is accepted/discussed. [1] https://bugzilla.gnome.org/show_bug.cgi?id=762138 *** Bug 1513915 has been marked as a duplicate of this bug. *** libsoup-2.60.2-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc4ed61dfc libsoup-2.60.2-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc4ed61dfc libsoup-2.60.2-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 1520114 has been marked as a duplicate of this bug. *** *** Bug 1552888 has been marked as a duplicate of this bug. *** *** Bug 1436680 has been marked as a duplicate of this bug. *** *** Bug 1472779 has been marked as a duplicate of this bug. *** *** Bug 1459168 has been marked as a duplicate of this bug. *** |