Bug 535571 - g_base64_encode_step: assertion 'in != NULL' failed and more error messages in terminal
Summary: g_base64_encode_step: assertion 'in != NULL' failed and more error messages i...
Status: CLOSED DUPLICATE of bug 530781
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, investigate, lts, regression
Depends on:
Blocks:
 
Reported: 2018-06-05 20:22 EDT by Mustafa Kocaturk CLA
Modified: 2018-06-06 06:34 EDT (History)
2 users (show)

See Also:


Attachments
Log on latest photon (34.68 KB, text/x-log)
2018-06-06 04:24 EDT, Wim Jongman CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mustafa Kocaturk CLA 2018-06-05 20:22:50 EDT
The following error messages are printed when eclipse is started from command line.

[several hundred similar lines clipped ...]
(Eclipse:13715): GLib-CRITICAL **: 19:58:19.810: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:13715): GLib-CRITICAL **: 19:58:19.810: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:13715): GLib-CRITICAL **: 19:58:19.811: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:13715): GLib-CRITICAL **: 19:58:19.811: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:13715): GLib-CRITICAL **: 19:58:19.827: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:13715): GLib-CRITICAL **: 19:58:19.827: g_base64_encode_step: assertion 'in != NULL' failed
org.eclipse.m2e.logback.configuration: Logback config file: /home/mlthost/eclipse-workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.8.3.20180227-2137.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://1031.fwk538441446:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://1031.fwk538441446:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
org.eclipse.m2e.logback.configuration: Initializing logback
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.emf.ecore.xmi.impl.XMLHandler (file:/snap/eclipse/12/plugins/org.eclipse.emf.ecore.xmi_2.13.0.v20170609-0707.jar) to method com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of org.eclipse.emf.ecore.xmi.impl.XMLHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

(Eclipse:13715): Gtk-WARNING **: 19:58:24.341: gtk_widget_size_allocate(): attempt to allocate widget with width 12 and height -12

(Eclipse:13715): Gtk-CRITICAL **: 19:58:24.341: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(Eclipse:13715): Gtk-WARNING **: 19:58:25.648: Negative content width -5 (allocation 1, extents 3x3) while allocating gadget (node progressbar, owner GtkProgressBar)

(Eclipse:13715): Gtk-WARNING **: 19:58:25.648: Negative content width -2 (allocation 0, extents 1x1) while allocating gadget (node trough, owner GtkProgressBar)
[... several hundred similar lines clipped]


-- Configuration Details --
Product: Eclipse 4.7.3.20180405-1200 (org.eclipse.epp.package.java.product)Installed Features:
 org.eclipse.platform 4.7.3.v20180330-0640
Comment 1 Wim Jongman CLA 2018-06-06 04:24:18 EDT
Created attachment 274343 [details]
Log on latest photon

I also see this on latest photon.
Comment 2 Wim Jongman CLA 2018-06-06 04:25:00 EDT
(In reply to Wim Jongman from comment #1)
> Created attachment 274343 [details]
> Log on latest photon
> 
> I also see this on latest photon.

There are no problems running by the way. Everything functions normally.
Comment 3 Dani Megert CLA 2018-06-06 06:24:15 EDT
(In reply to Wim Jongman from comment #1)
> Created attachment 274343 [details]
> Log on latest photon
> 
> I also see this on latest photon.

Can you check whether this is something new? E.g. try with 4.7.
Comment 4 Dani Megert CLA 2018-06-06 06:34:42 EDT

*** This bug has been marked as a duplicate of bug 530781 ***