<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>188349</bug_id>
          
          <creation_ts>2018-08-06 11:32:58 -0700</creation_ts>
          <short_desc>FATAL: Primitive gigacage disabled, but we don&apos;t want that in this process</short_desc>
          <delta_ts>2018-08-06 11:32:58 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>New Bugs</component>
          <version>Other</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Anton Lindström">hlewagastir</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1448181</commentid>
    <comment_count>0</comment_count>
    <who name="Anton Lindström">hlewagastir</who>
    <bug_when>2018-08-06 11:32:58 -0700</bug_when>
    <thetext>After upgrading from webkit-gtk-2.18.6 to webkit-gtk-2.20.3 creating reports in GnuCash fails (it uses webkit-gtk for rendering) and this error is printed to the terminal:

FATAL: Primitive gigacage disabled, but we don&apos;t want that in this process

I managed to trace this to having
ulimit -v 9500000
set. With 
ulimit -v unlimited
all works as expected.

I think this is related to bug 183329 -- that&apos;s the one that gave me the clue that the problem was connected to the virtual memory limit.
(I have vm.overcommit_memory = 0 if that makes any difference)

At least I think the error message should be nicer even if it&apos;s &quot;supposed to&quot; fail.

Running Gentoo Linux on x86.

Kind regards,
Anton</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>