Bug 415681 - Eclipse crashes with return code -1073740771
Summary: Eclipse crashes with return code -1073740771
Status: CLOSED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2013-08-22 09:56 EDT by Moritz Geist CLA
Modified: 2019-09-23 08:10 EDT (History)
4 users (show)

See Also:


Attachments
extract of the log in the workspace (1.15 KB, application/octet-stream)
2013-08-22 09:56 EDT, Moritz Geist CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Geist CLA 2013-08-22 09:56:17 EDT
Created attachment 234662 [details]
extract of the log in the workspace

Crash is reproducable, it appears while Code Completion of a Enum ( <enum>.name()).
It doesn´t appear while completing normal java classes.

In the .log file of my Workspace is an EGit error (see attachment), altough im not using egit.

System info:
64bit, 8GB Ram, Win7 HP.

More info: http://show.picr.de/15584785ce.png.html
Comment 1 Dani Megert CLA 2013-08-22 10:06:49 EDT
Please attach the crash log (either near eclipse.exe or where your JRE is).
Comment 2 Moritz Geist CLA 2013-08-22 11:34:39 EDT
didnt find it.

there is no file containing "log" in his name or so in the Java and eclipse directories. The only log i have is the one from the workspace. Starting eclipse in debugmode doesnt help.
Comment 3 Dani Megert CLA 2013-08-23 03:01:52 EDT
(In reply to comment #2)
> didnt find it.
> 
> there is no file containing "log" in his name or so in the Java and eclipse
> directories. The only log i have is the one from the workspace. Starting
> eclipse in debugmode doesnt help.

It would be hs_err_pid<pid>.log

You can also specify it with: -XX:ErrorFile=/path/to/file.
Comment 4 Moritz Geist CLA 2013-08-23 06:16:43 EDT
Tried this too, but it did not work. Only the window from the screenshot and the attached log. Tried to force a stacktrace via jStack too.

"Eclipse stopped responding", thats the only thing windows says to the error.
Comment 5 Dani Megert CLA 2013-08-23 06:35:22 EDT
(In reply to comment #4)
> Tried this too, but it did not work. Only the window from the screenshot and
> the attached log. Tried to force a stacktrace via jStack too.
> 
> "Eclipse stopped responding", thats the only thing windows says to the error.

Try to use eclipsec.exe instead of eclipse.exe and use java.exe instead of javaw.exe.
Comment 6 Michael Seele CLA 2019-09-23 08:06:33 EDT
We get the same crash with a standalone swt/jface application with the latest swt/jface version 4.13.
JVM dies silently with exit code -1073740771 without an error log. Windows event log shows the following:

---------------------------------------------
Name der fehlerhaften Anwendung: javaw.exe, Version: 11.0.4.0, Zeitstempel: 0x5d2f4180
Name des fehlerhaften Moduls: MSCTF.dll, Version: 10.0.18362.356, Zeitstempel: 0x1b84914f
Ausnahmecode: 0xc000041d
Fehleroffset: 0x000000000002ab68
ID des fehlerhaften Prozesses: 0x172ac
Startzeit der fehlerhaften Anwendung: 0x01d572070990721f
Pfad der fehlerhaften Anwendung: C:\dev\java\jdk-11\bin\javaw.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\MSCTF.dll
Berichtskennung: ac2dbde3-8c29-4ff5-b487-92db7cc1ef4f
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
---------------------------------------------
Fehlerbucket 1799010330721225264, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: javaw.exe
P2: 11.0.4.0
P3: 5d2f4180
P4: MSCTF.dll
P5: 10.0.18362.356
P6: 1b84914f
P7: c000041d
P8: 000000000002ab68
P9: 
P10: 

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C95.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DAF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DD0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DD0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E0F.tmp.txt

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: ac2dbde3-8c29-4ff5-b487-92db7cc1ef4f
Berichtstatus: 268435456
Bucket mit Hash: 8f7b9a369ac44d7a08f75e5d3de58a30
CAB-Datei-Guid: 0
---------------------------------------------

Maybe a comeback of https://bugs.eclipse.org/bugs/show_bug.cgi?id=526758 ?
Comment 7 Andrey Loskutov CLA 2019-09-23 08:09:26 EDT
(In reply to Michael Seele from comment #6)
> We get the same crash with a standalone swt/jface application with the
> latest swt/jface version 4.13.
> Maybe a comeback of https://bugs.eclipse.org/bugs/show_bug.cgi?id=526758 ?

Please open a new bug for that, it doesn't make sense to resurrect this old one. 

But before, please check if you have toggled EGit search toolbar on/off, see bug 551067.
Comment 8 Andrey Loskutov CLA 2019-09-23 08:10:10 EDT
No reaction for years, closing.