Bug 837031

Summary:	YaST got signal 11 at YCP file on installation start (Segmentation fault)
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Rick Salevsky <rsalevsky>
Component:	YaST2	Assignee:	Josef Reidinger <jreidinger>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	jreidinger, trenn
Version:	13.1 Milestone 4
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rick Salevsky 2013-08-27 14:55:47 UTC

When I start an installation of openSuse Factory, in the first seconds the following error message during installation shows up and the process stops:

*** Starting YaST2 ***
Out of memory!
YaST got signal 11 at YCP file /mounts/mp_0001/usr/share/YaST2/modules/Storage.rb:2343
/usr/lib/YaST2/startup/YaST2.call: line 277:  3793 Segmentation fault $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS
ain:~ # Connection to ain closed by remote host.

The "Out of Memory" message makes no sense for me because the Machine has 31900 MB RAM.

I also realized that the build of openSUSE:Factory yast2-storage fails. I don't know if this is the reason, but it looks wrong :P
https://build.opensuse.org/package/show/openSUSE:Factory/yast2-storage

Comment 2 Josef Reidinger 2013-08-28 09:34:08 UTC

OK, lets check what is going wrong and if I can reproduce it. Interesting part is that it doesn't fail in openqa which had only 1GB of memory (kvm virtualization). Can you please be more specify if you run installation in virtual environment and what if yes or details of your hardware setup.
Thanks

Comment 5 Josef Reidinger 2013-08-28 12:06:57 UTC

Thomas (Fehr) - Could you check this image? I found that it fails somewhere in perl bindings for libstorage - call perl_sv_setpvn http://perldoc.perl.org/perlguts.html#Working-with-SVs .
I am not sure what cause it, as it can be from problem in SWIG, problem in ruby-bindings that pass something bad to perl-bindings or somewhere else. But I think that you in past change yast2-storage to use libstorage-ruby, so maybe problem can be in this part, that it load something wrong.

Thanks ( I will continue investigating it )

I reproduce it when I start installation and in storage click on propose btrfs partitions, so it happen on various places ( so maybe garbage collector is in action ).

Comment 6 Josef Reidinger 2013-08-28 12:20:31 UTC

After another round of debugging and investigating I found that problem is that inst-sys contain yast2-storage 3.0.0 even if factory contain 3.0.2, that no longer have dependency on perl. So I check why this image doesn't have it.

Comment 7 Thomas Fehr 2013-08-28 12:48:03 UTC

Of course it is essential that one uses both of libstorage/yast2-storage from
what is available in YaST2:Head of from Milestone#4. What you observe could
very well happen if one uses libstorage from YaST2:Head together with
yast2-storage from Milestone#4 sine we removed the cruft needed for
yast2-perl-bindings from libstorage after converting yast2-storage to 
use ruby bindings instead.

BTW: if I look into the link mentioned in comment#1, I can only see that
yast2-storage builds. But there is also a text that a submitrequest for
yast2-storage was accepted 17 hours ago so maybe Factory simply 
contained outdated yast2-storage when mentioned Image was created.

Comment 8 Julian Wolf 2013-09-02 09:26:36 UTC

Tested and seems to work now.