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

iSecureOS crashing with “Should perform in-depth scan” enabled #15

Open
jkole4 opened this issue Jun 10, 2021 · 3 comments
Open

iSecureOS crashing with “Should perform in-depth scan” enabled #15

jkole4 opened this issue Jun 10, 2021 · 3 comments

Comments

@jkole4
Copy link

jkole4 commented Jun 10, 2021

Every time I enable "should perform in-depth scan" iSecureOS crashes. The last thing I see it scanning is /usr/libexec/git-core/git-rebase--preserve-merges. Scanning without it enabled will make it scan successfully and not crash.

Cr4shed Report 1

Date: 6/10/21, 10:48 PM
Process: iSecureOS
Bundle id: com.geosn0w.iSecureOS
Device: iPhone X, iOS 14.3

Reason: The process was terminated for exceeding jetsam memory limits
Uptime: 10s
Virtual memory size: 0x61e53b0000 bytes
Resident memory size: 0x390000 bytes
CPU usage: 0%
Thread count: 16

Binary Images:
0x1889d0000 - 0x189d99fff UIKitCore arm64 <3405666F-F281-3F71-BA86-83E5A27AB5B0> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore
0x18e178000 - 0x18e18ffff AudioSession arm64 <2F01B093-A18B-3FC5-9A63-7795E46A4CFD> /System/Library/PrivateFrameworks/AudioSession.framework/AudioSession
0x189db8000 - 0x18a02dfff QuartzCore arm64 /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x1b2acd000 - 0x1b2afdfff libsystem_kernel.dylib arm64 <70F0BF28-5A58-32C7-B85E-ED47A2216291> /usr/lib/system/libsystem_kernel.dylib
0x187e27000 - 0x1880c1fff Foundation arm64 /System/Library/Frameworks/Foundation.framework/Foundation
0x18686d000 - 0x1868ebfff libdispatch.dylib arm64 <04B54A98-8EAD-371E-8C12-AD116CB118E2> /usr/lib/system/libdispatch.dylib
0x102128000 - 0x10213ffff iSecureOS arm64 <7A027B10-B15D-3968-8270-87013411ECDA> /Applications/iSecureOS.app/iSecureOS
0x1868ec000 - 0x186922fff libdyld.dylib arm64 /usr/lib/system/libdyld.dylib
0x19d949000 - 0x19d951fff GraphicsServices arm64 <74274083-05FA-31B3-A3F1-1216855C910A> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x186b7b000 - 0x186f24fff CoreFoundation arm64 <6FD5304A-9759-3E22-A863-456EAB55F4CC> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x1cf330000 - 0x1cf340fff libsystem_pthread.dylib arm64 /usr/lib/system/libsystem_pthread.dylib

{"ProcessBundleID":"com.geosn0w.iSecureOS","NSExceptionReason":"The process was terminated for exceeding jetsam memory limits","ProcessName":"iSecureOS"}

Cr4shed report 2

Date: 6/10/21, 10:47 PM
Process: iSecureOS
Bundle id: com.geosn0w.iSecureOS
Device: iPhone X, iOS 14.3

Reason: The process was terminated for exceeding jetsam memory limits
Uptime: 41s
Virtual memory size: 0x6040000000 bytes
Resident memory size: 0x0 bytes
CPU usage: 0%
Thread count: 14

Binary Images not found

{"ProcessBundleID":"com.geosn0w.iSecureOS","NSExceptionReason":"The process was terminated for exceeding jetsam memory limits","ProcessName":"iSecureOS"}

Recent items installed

Theos + dependencies
Taurine 1.0.6 rc1

@jkole4
Copy link
Author

jkole4 commented Jun 10, 2021

Also scanning with tweaks disabled with not do anything  either still crashes

@GeoSn0w
Copy link
Owner

GeoSn0w commented Sep 19, 2021

The process was terminated for exceeding jetsam memory limits seems to be indicating that the hashing takes too much memory and jetsam forces the app closed. Will fix.

@Tokarak
Copy link

Tokarak commented Apr 16, 2022

I too was suffering from this problem. Fortunately I had half a gigabyte of old dependencies which I cleaned through apt-get auto-remove, after which the scan worked with no crash.

Yet even now, the peak of memory usage during a scan was 700mb - dangerously high on a 2gb ram device. It is possible the app os crashing because the device physically cannot allocate any more memory, and just increasing jetsam will lead to springboard crashing instead.

The best way to fix this is to release memory during a scan. Right now it seems memory is released only at the end, which anyone can see will lead to problems like this. Once a file is scanned, there is no need to retain it in memory, and it should be released.

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