Project

General

Profile

Actions
Copy link

Bug #43059

open

mgr/dashboard: generate source maps for front-end code

Added by Ernesto Puerta over 4 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Build, CI, Dependencies & Tools
Target version:
Ceph - v15.0.0
% Done:

0%

Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Currently, front-end code, when built and packaged, becomes hard to debug (it's transpiled and minified), so by generating and packaging source maps during production builds would be really helpful for debugging (adding --sourcemap to --prod builds).

Actions
Copy link
 #1

Updated by Ernesto Puerta over 4 years ago

The webpack Terser plugin aborts with a core dump due to OOM:

Environment variables have been set
 92% chunk asset optimization TerserPlugin                                         
<--- Last few GCs --->

[31502:0x3b41a10]   158565 ms: Scavenge 1336.5 (1422.9) -> 1335.8 (1423.4) MB, 9.7 / 0.0 ms  (average mu = 0.216, current mu = 0.155) allocation failure 
[31502:0x3b41a10]   158576 ms: Scavenge 1336.7 (1423.4) -> 1336.0 (1424.4) MB, 7.8 / 0.0 ms  (average mu = 0.216, current mu = 0.155) allocation failure 
[31502:0x3b41a10]   158583 ms: Scavenge 1336.9 (1424.4) -> 1336.2 (1424.9) MB, 4.7 / 0.0 ms  (average mu = 0.216, current mu = 0.155) allocation failure 

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0xd6e4ff5be1d]
    1: StubFrame [pc: 0xd6e4ff047bb]
    2: ConstructFrame [pc: 0xd6e4ff0d145]
Security context: 0x05f66fe1e6e9 <JSObject>
    3: DoJoin(aka DoJoin) [0x5f66fe05e91] [native array.js:~87] [pc=0xd6e524d104d](this=0x0142594026f1 <undefined>,l=0x156164aa8631 <JSArray[13]>,m=13,A=0x0142594028c9 <true>,w=0x324350bb1bf1 <String[1]: />,v=0x0142594029a1 <false>)
    4: Join(aka Join) [0x5f66fe05ee1] [native arr...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x8f9d10 node::Abort() [ng build --prod --sourceMap]
 2: 0x8f9d5c  [ng build --prod --sourceMap]
 3: 0xaffd0e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [ng build --prod --sourceMap]
 4: 0xafff44 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [ng build --prod --sourceMap]
 5: 0xef4152  [ng build --prod --sourceMap]
 6: 0xef4258 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [ng build --prod --sourceMap]
 7: 0xf00332 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [ng build --prod --sourceMap]
 8: 0xf00c64 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [ng build --prod --sourceMap]
 9: 0xf038d1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [ng build --prod --sourceMap]
10: 0xeccd54 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [ng build --prod --sourceMap]
11: 0x116cede v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [ng build --prod --sourceMap]
12: 0xd6e4ff5be1d 
Aborted (core dumped)
Actions
Copy link
 #2

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 160 to Build, CI, Dependencies & Tools
Actions
Copy link

Also available in: Atom PDF