Bug 188349 - FATAL: Primitive gigacage disabled, but we don't want that in this process
Summary: FATAL: Primitive gigacage disabled, but we don't want that in this process
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: Other
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-06 11:32 PDT by Anton Lindström
Modified: 2018-08-06 11:32 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Lindström 2018-08-06 11:32:58 PDT 
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'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'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's "supposed to" fail.

Running Gentoo Linux on x86.

Kind regards,
Anton