Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash(OutOfMemory) for a picture #62

Open
thynson opened this issue Mar 16, 2017 · 2 comments
Open

Crash(OutOfMemory) for a picture #62

thynson opened this issue Mar 16, 2017 · 2 comments

Comments

@thynson
Copy link

thynson commented Mar 16, 2017

Using exif-cli tool to get exif info for this picture, got the belowing crash log.

% exif ~/Desktop/7746950.jpg 


<--- Last few GCs --->

[25939:0x104001c00]     2534 ms: Mark-sweep 358.6 (363.9) -> 358.6 (363.9) MB, 147.7 / 0.0 ms  last resort 
[25939:0x104001c00]     3485 ms: Mark-sweep 890.9 (896.2) -> 536.0 (542.3) MB, 180.4 / 0.0 ms  (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 951 ms) allocation failure GC in old space requested


<--- JS stacktrace --->

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

Security context: 0x173c292a66a1 <JS Object>
    2: extractExifEntry [/usr/local/lib/node_modules/exif-cli/node_modules/exif/lib/exif/ExifImage.js:~270] [pc=0x17bf542ef0c](this=0x11929f3cbeb9 <an ExifImage with map 0x2af1821442b1>,data=0x11929f3cbf51 <an Uint8Array with map 0x2af18212c9f1>,entryOffset=1086,tiffOffset=12,isBigEndian=0x38eda7182421 <false>,tags=0x11929f3f6681 <an Object with map 0x2af182102c51>)
    3: extractExifData [/usr...

FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 5: v8::internal::Heap::AllocateRawFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
 6: v8::internal::Heap::AllocateUninitializedFixedArray(int) [/usr/local/bin/node]
 7: v8::internal::Factory::NewUninitializedFixedArray(int) [/usr/local/bin/node]
 8: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedObjectElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)2> >::GrowCapacity(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/usr/local/bin/node]
 9: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
10: 0x17bf52843a7
11: 0x17bf542624c
[1]    25939 abort      exif ~/Desktop/7746950.jpg
@bripkens
Copy link

Got a similar situation for another picture. Any idea what might be the cause?

@losik2
Copy link

losik2 commented Jun 22, 2018

I have same prolem. Temporary fix is a start application with more memory limit node --max-old-space-size=4096 app.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants