FATAL EXCEPTION: java.lang.OutOfMemoryError: EnsureLocalCapacity (FileInputStream.open0,...
After upgrading BuildTools from 23 to 27 I faced issue with crash.
I've checked RAM usage in profiler - there's no anomaly there. App crashes sometimes in background, sometimes in foreground, in different activities (crash is completely nondeterministic), it doesn't seems to depend on memory usage (was able to crash with 350mb usage like also with 200mb)
I also installed 'square/leakcanary' to find any memoryleaks, but nothing's there...
Seems to be a problem with loading native typeface. I don't use custom font in this application. I managed to crash app on Samsung S9 and Samsung S5. Any ideas? :(
Thanks for any help!
Stacktrace:
2018-10-05 08:09:04.740 20542-20542/pl.chillout.debug E/AndroidRuntime: FATAL EXCEPTION: main
Process: pl.chillout.debug, PID: 20542
java.lang.OutOfMemoryError: EnsureLocalCapacity
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:200)
at java.io.FileInputStream.<init>(FileInputStream.java:150)
at android.graphics.Typeface.getFullFlipFont(Typeface.java:1275)
at android.graphics.Typeface.getFontPathFlipFont(Typeface.java:1220)
at android.graphics.Typeface.SetFlipFonts(Typeface.java:1413)
at android.graphics.Typeface.SetAppTypeFace(Typeface.java:1547)
at android.app.Activity.onCreate(Activity.java:1020)
at android.support.v4.app.SupportActivity.onCreate(SupportActivity.java:66)
at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:321)
at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:84)
at pl.chillout.redesign.activity.BaseDrawerActivity.onCreate(BaseDrawerActivity.java:45)
at pl.chillout.redesign.activity.ChilloutActivity.onCreate(ChilloutActivity.java:115)
at android.app.Activity.performCreate(Activity.java:7174)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
java android memory-leaks crash
|
show 3 more comments
After upgrading BuildTools from 23 to 27 I faced issue with crash.
I've checked RAM usage in profiler - there's no anomaly there. App crashes sometimes in background, sometimes in foreground, in different activities (crash is completely nondeterministic), it doesn't seems to depend on memory usage (was able to crash with 350mb usage like also with 200mb)
I also installed 'square/leakcanary' to find any memoryleaks, but nothing's there...
Seems to be a problem with loading native typeface. I don't use custom font in this application. I managed to crash app on Samsung S9 and Samsung S5. Any ideas? :(
Thanks for any help!
Stacktrace:
2018-10-05 08:09:04.740 20542-20542/pl.chillout.debug E/AndroidRuntime: FATAL EXCEPTION: main
Process: pl.chillout.debug, PID: 20542
java.lang.OutOfMemoryError: EnsureLocalCapacity
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:200)
at java.io.FileInputStream.<init>(FileInputStream.java:150)
at android.graphics.Typeface.getFullFlipFont(Typeface.java:1275)
at android.graphics.Typeface.getFontPathFlipFont(Typeface.java:1220)
at android.graphics.Typeface.SetFlipFonts(Typeface.java:1413)
at android.graphics.Typeface.SetAppTypeFace(Typeface.java:1547)
at android.app.Activity.onCreate(Activity.java:1020)
at android.support.v4.app.SupportActivity.onCreate(SupportActivity.java:66)
at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:321)
at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:84)
at pl.chillout.redesign.activity.BaseDrawerActivity.onCreate(BaseDrawerActivity.java:45)
at pl.chillout.redesign.activity.ChilloutActivity.onCreate(ChilloutActivity.java:115)
at android.app.Activity.performCreate(Activity.java:7174)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
java android memory-leaks crash
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
1
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14
|
show 3 more comments
After upgrading BuildTools from 23 to 27 I faced issue with crash.
I've checked RAM usage in profiler - there's no anomaly there. App crashes sometimes in background, sometimes in foreground, in different activities (crash is completely nondeterministic), it doesn't seems to depend on memory usage (was able to crash with 350mb usage like also with 200mb)
I also installed 'square/leakcanary' to find any memoryleaks, but nothing's there...
Seems to be a problem with loading native typeface. I don't use custom font in this application. I managed to crash app on Samsung S9 and Samsung S5. Any ideas? :(
Thanks for any help!
Stacktrace:
2018-10-05 08:09:04.740 20542-20542/pl.chillout.debug E/AndroidRuntime: FATAL EXCEPTION: main
Process: pl.chillout.debug, PID: 20542
java.lang.OutOfMemoryError: EnsureLocalCapacity
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:200)
at java.io.FileInputStream.<init>(FileInputStream.java:150)
at android.graphics.Typeface.getFullFlipFont(Typeface.java:1275)
at android.graphics.Typeface.getFontPathFlipFont(Typeface.java:1220)
at android.graphics.Typeface.SetFlipFonts(Typeface.java:1413)
at android.graphics.Typeface.SetAppTypeFace(Typeface.java:1547)
at android.app.Activity.onCreate(Activity.java:1020)
at android.support.v4.app.SupportActivity.onCreate(SupportActivity.java:66)
at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:321)
at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:84)
at pl.chillout.redesign.activity.BaseDrawerActivity.onCreate(BaseDrawerActivity.java:45)
at pl.chillout.redesign.activity.ChilloutActivity.onCreate(ChilloutActivity.java:115)
at android.app.Activity.performCreate(Activity.java:7174)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
java android memory-leaks crash
After upgrading BuildTools from 23 to 27 I faced issue with crash.
I've checked RAM usage in profiler - there's no anomaly there. App crashes sometimes in background, sometimes in foreground, in different activities (crash is completely nondeterministic), it doesn't seems to depend on memory usage (was able to crash with 350mb usage like also with 200mb)
I also installed 'square/leakcanary' to find any memoryleaks, but nothing's there...
Seems to be a problem with loading native typeface. I don't use custom font in this application. I managed to crash app on Samsung S9 and Samsung S5. Any ideas? :(
Thanks for any help!
Stacktrace:
2018-10-05 08:09:04.740 20542-20542/pl.chillout.debug E/AndroidRuntime: FATAL EXCEPTION: main
Process: pl.chillout.debug, PID: 20542
java.lang.OutOfMemoryError: EnsureLocalCapacity
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:200)
at java.io.FileInputStream.<init>(FileInputStream.java:150)
at android.graphics.Typeface.getFullFlipFont(Typeface.java:1275)
at android.graphics.Typeface.getFontPathFlipFont(Typeface.java:1220)
at android.graphics.Typeface.SetFlipFonts(Typeface.java:1413)
at android.graphics.Typeface.SetAppTypeFace(Typeface.java:1547)
at android.app.Activity.onCreate(Activity.java:1020)
at android.support.v4.app.SupportActivity.onCreate(SupportActivity.java:66)
at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:321)
at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:84)
at pl.chillout.redesign.activity.BaseDrawerActivity.onCreate(BaseDrawerActivity.java:45)
at pl.chillout.redesign.activity.ChilloutActivity.onCreate(ChilloutActivity.java:115)
at android.app.Activity.performCreate(Activity.java:7174)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3030)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
java android memory-leaks crash
java android memory-leaks crash
asked Oct 5 at 6:51
Cililing
415110
415110
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
1
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14
|
show 3 more comments
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
1
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
1
1
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14
|
show 3 more comments
3 Answers
3
active
oldest
votes
See if explicitly specifying default font in all your views fixes the issue. It looks like it's trying to load a font that doesn't exist.
<TextView
.....
android:fontFamily="sans-serif" />
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
add a comment |
the reason for this situation maybe you are using static objects like that :
private static TextView textView; //DO NOT DO THIS
private static Context context; //DO NOT DO THIS
this is the first sign of a memory leak.
Unfortunately there is no full code
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
add a comment |
Dear add largeheap=true in manifest. then finish started activities. And check your drawable dimension (size). I faced this issue in PagerView. I resize drawable images. and finish all activity. and largheap now crash is removed. I think your error related to orio devices please initialize all objects for orio devices.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52659856%2ffatal-exception-java-lang-outofmemoryerror-ensurelocalcapacity-fileinputstrea%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
See if explicitly specifying default font in all your views fixes the issue. It looks like it's trying to load a font that doesn't exist.
<TextView
.....
android:fontFamily="sans-serif" />
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
add a comment |
See if explicitly specifying default font in all your views fixes the issue. It looks like it's trying to load a font that doesn't exist.
<TextView
.....
android:fontFamily="sans-serif" />
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
add a comment |
See if explicitly specifying default font in all your views fixes the issue. It looks like it's trying to load a font that doesn't exist.
<TextView
.....
android:fontFamily="sans-serif" />
See if explicitly specifying default font in all your views fixes the issue. It looks like it's trying to load a font that doesn't exist.
<TextView
.....
android:fontFamily="sans-serif" />
answered Nov 13 at 5:37
AardvarkBlue
264
264
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
add a comment |
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
Why do you think so? Crash is not deterministic, and existance of font is.
– Cililing
Nov 13 at 8:20
1
1
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
Not necessarily, if you create, recreate, or use a TextView only under certain circumstances. That may explain why the crash occurs during onCreate. FWITW, you can find similar bugs in any app if you turn on StrictMode and simply call onCreate. If you are not getting error often, you may consider ignoring it.
– AardvarkBlue
Nov 13 at 8:29
add a comment |
the reason for this situation maybe you are using static objects like that :
private static TextView textView; //DO NOT DO THIS
private static Context context; //DO NOT DO THIS
this is the first sign of a memory leak.
Unfortunately there is no full code
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
add a comment |
the reason for this situation maybe you are using static objects like that :
private static TextView textView; //DO NOT DO THIS
private static Context context; //DO NOT DO THIS
this is the first sign of a memory leak.
Unfortunately there is no full code
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
add a comment |
the reason for this situation maybe you are using static objects like that :
private static TextView textView; //DO NOT DO THIS
private static Context context; //DO NOT DO THIS
this is the first sign of a memory leak.
Unfortunately there is no full code
the reason for this situation maybe you are using static objects like that :
private static TextView textView; //DO NOT DO THIS
private static Context context; //DO NOT DO THIS
this is the first sign of a memory leak.
Unfortunately there is no full code
answered Nov 13 at 7:56
Gökhan Musapaşaoğlu ヅ
1014
1014
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
add a comment |
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
No, I've looked for memory leaks before I wrote this question.
– Cililing
Nov 13 at 8:14
add a comment |
Dear add largeheap=true in manifest. then finish started activities. And check your drawable dimension (size). I faced this issue in PagerView. I resize drawable images. and finish all activity. and largheap now crash is removed. I think your error related to orio devices please initialize all objects for orio devices.
add a comment |
Dear add largeheap=true in manifest. then finish started activities. And check your drawable dimension (size). I faced this issue in PagerView. I resize drawable images. and finish all activity. and largheap now crash is removed. I think your error related to orio devices please initialize all objects for orio devices.
add a comment |
Dear add largeheap=true in manifest. then finish started activities. And check your drawable dimension (size). I faced this issue in PagerView. I resize drawable images. and finish all activity. and largheap now crash is removed. I think your error related to orio devices please initialize all objects for orio devices.
Dear add largeheap=true in manifest. then finish started activities. And check your drawable dimension (size). I faced this issue in PagerView. I resize drawable images. and finish all activity. and largheap now crash is removed. I think your error related to orio devices please initialize all objects for orio devices.
answered Nov 13 at 11:00
adil khan
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52659856%2ffatal-exception-java-lang-outofmemoryerror-ensurelocalcapacity-fileinputstrea%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you manage to fix it? I just caught the same crash on Samsung Galaxy S7
– Maksim Dmitriev
Nov 6 at 10:55
Unfortunately not :(
– Cililing
Nov 7 at 7:55
If your pc is with x64 operating system, can u please check if the project is NOT saved under Program Files x86? If so, please cut and paste it elsewhere like Program Files or your desktop and try again.
– Eray Balkanli
Nov 11 at 5:37
1
can you post the code?
– Abdul Aziz
Nov 12 at 12:19
with a high probability it is not a hardware failure
– Oleg Ushakov
Nov 13 at 7:14