GNOME Bugzilla – Bug 711219
Crash of soup, resulting in crash of JRE (exhibited in eclipse)
Last modified: 2013-10-31 16:43:06 UTC
I was able to predictably crash eclipse (after booting it up the first time after an update), and tried to find the source. Well, easy: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f61e624ec71, pid=6486, tid=140061130299136 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libsoup-2.4.so.1+0x6ec71] soup_session_feature_detach+0x11 The crash in libsoup let's also crash the JRE, making every java application that uses libsoup vulnerable, not only Eclipse. Surprisingly, there has been a bugreport on debian's platform for quite a while now, even including a patch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705420#30 I applied the bug, which was as easy as expected. Since libsoup2.4-1's source doesn't come with a list which packages are required for building, I had to try and err a while. make install, and eclipse runs as stable as before the update again. When I queried this Bugzilla (Using https://bugzilla.gnome.org/buglist.cgi?query_format=specific&order=rel evance+desc&bug_status=__open__&product=libsoup&content=crash ), I couldn't see any bug report that mention this behaviour. These are what the query returned just before creation of this report: 643072 cri Nor Linu libsoup UNCO Crash when calling soup_cache_dump 684265 nor Nor Linu libsoup UNCO crash in SoupServer if interface property is not resolved 651032 maj Nor Linu libsoup UNCO calling g_object_unref(session) after soup_session_cancel_message()/soup_session_abort() can make crash while processing soup_session_send_message() in sync session. 710602 min Nor All libsoup UNCO Assertion failure in soup_server_unpause_message() for unsent messages 561547 nor Nor Linu libsoup NEW soup_server_new() might return NULL 665884 nor Nor Linu libsoup REOP SoupCache: do not store headers on cache index Since the bug crashed an application multiple times within few minutes of usage, I'm going to rate this as blocker, as Eclipse became completely unusable for me after updating to the newest libsoup version. I'm sure there are more people that are affected by this, but most just don't reach this page. In order to make it easier for you, I attach the linked patch to this report. This is not my work, all credits go to twied. With regards, Ben
This is an eclipse bug that has already been fixed upstream (as mentioned at the end of the debian bug you linked to) *** This bug has been marked as a duplicate of bug 710242 ***
Created attachment 258675 [details] [review] Proposed patch, copied from http://bugs.debian.org As far as I can see, this fixes the crashes in Eclipse. This is copied from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705420#30 This is not my work, all credits go to twied.