Bug 979099

Summary: [abrt] kde-workspace-4.10.4-1.fc18: FixedVMPoolAllocator: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: René Romero Benavides <rene.romero.b>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rene.romero.b, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4f9f3c4e7fd3fe437d98061cee737dbf6a45fc1f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-27 18:35:09 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 Flags
File: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors none

Description René Romero Benavides 2013-06-27 15:17:27 UTC 
Description of problem:
Instaled updates up to June 26 and the kvm stack, nothing else, the kde environment doesn't work unless in failsafe mode from then on.

Version-Release number of selected component:
kde-workspace-4.10.4-1.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/bin/plasma-desktop --nocrashhandler
core_backtrace: 
crash_function: FixedVMPoolAllocator
executable:     /usr/bin/plasma-desktop
kernel:         3.9.6-200.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 FixedVMPoolAllocator at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:310
 #1 QTJSC::ExecutablePool::systemAlloc at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:443
 #2 ExecutablePool at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:258
 #3 create at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:97
 #4 ExecutableAllocator at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:150
 #5 QTJSC::JSGlobalData::JSGlobalData at ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSGlobalData.cpp:146
 #6 QTJSC::JSGlobalData::create at ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSGlobalData.cpp:205
 #7 QScriptEnginePrivate::QScriptEnginePrivate at api/qscriptengine.cpp:979
 #8 QScriptEngine::QScriptEngine at api/qscriptengine.cpp:1964
 #9 QDeclarativeScriptEngine::QDeclarativeScriptEngine at qml/qdeclarativeengine.cpp:385
Comment 1 René Romero Benavides 2013-06-27 15:17:33 UTC 
Created attachment 766209 [details]
File: backtrace
Comment 2 René Romero Benavides 2013-06-27 15:17:38 UTC 
Created attachment 766210 [details]
File: cgroup
Comment 3 René Romero Benavides 2013-06-27 15:17:42 UTC 
Created attachment 766211 [details]
File: dso_list
Comment 4 René Romero Benavides 2013-06-27 15:17:47 UTC 
Created attachment 766212 [details]
File: environ
Comment 5 René Romero Benavides 2013-06-27 15:17:51 UTC 
Created attachment 766213 [details]
File: limits
Comment 6 René Romero Benavides 2013-06-27 15:17:58 UTC 
Created attachment 766214 [details]
File: maps
Comment 7 René Romero Benavides 2013-06-27 15:18:04 UTC 
Created attachment 766215 [details]
File: open_fds
Comment 8 René Romero Benavides 2013-06-27 15:18:08 UTC 
Created attachment 766216 [details]
File: proc_pid_status
Comment 9 René Romero Benavides 2013-06-27 15:18:12 UTC 
Created attachment 766217 [details]
File: var_log_messages
Comment 10 René Romero Benavides 2013-06-27 15:18:16 UTC 
Created attachment 766218 [details]
File: xsession_errors
Comment 11 Rex Dieter 2013-06-27 16:53:25 UTC 
How much RAM/VM do you have?  It would appear the Qt JavaScript JIT is failing memory allocations.
Comment 12 René Romero Benavides 2013-06-27 17:11:09 UTC 
free -m
             total       used       free     shared    buffers     cached
Mem:          3755       2980        775          0         96       1456
-/+ buffers/cache:       1427       2328
Swap:         3759          0       3759

vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 0  0      0 737444  99324 1501148    0    0    78    20  145 1654  3  2 94  2
Comment 13 René Romero Benavides 2013-06-27 18:35:09 UTC 
I just found the cause, I was tuning a Postgresql server and in the book I'm reading "PostgreSQL High Performace" is adviced to set vm.overcommit=0 for a PostgreSQL server. Reset it to its default value and things are working again. Thanks for your time
Comment 14 René Romero Benavides 2013-06-27 18:42:46 UTC 
I'm sorry, the value that wm.overcommit was set to is 2, changed it to 0
Comment 15 Kevin Kofler 2013-06-30 19:42:28 UTC 

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