This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 238456 - after pressing CTRL+S, file is not saved in disk
Summary: after pressing CTRL+S, file is not saved in disk
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: Actions/Menu/Toolbar (show other bugs)
Version: 7.4
Hardware: PC Linux
: P1 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-16 13:33 UTC by adithyank
Modified: 2013-11-18 09:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
file shown in nb ide and linux less cmd kept adjacent (214.36 KB, image/png)
2013-11-16 13:33 UTC, adithyank 		Details
messages.log of this session (51.25 KB, text/x-log)
2013-11-16 13:33 UTC, adithyank 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description adithyank 2013-11-16 13:33:06 UTC 
Created attachment 142263 [details]
file shown in nb ide and linux less cmd kept adjacent

When I am typing code, after pressing CTRL+S, file is not saved in the disk.

How I identified this issue because of the following two signs

1. Tab title is bold
2. Compilation error did not get cleared from the editor

But, the status bar says "<filename> saved."

I am attaching the screenshot. pls notice the following discrepancies from this

1. status bar saying "saved" msg
2. tab title is bold
3. editor saying compilation error
4. less command showing some old version of the file
Comment 1 adithyank 2013-11-16 13:33:39 UTC 
Created attachment 142264 [details]
messages.log of this session
Comment 2 markiewb 2013-11-16 15:03:47 UTC 
SEVERE [org.openide.util.RequestProcessor]
java.lang.OutOfMemoryError: unable to create new native thread
	at java.lang.Thread.start0(Native Method)
	at java.lang.Thread.start(Thread.java:693)
	at org.netbeans.modules.mercurial.util.HgCommand.exec(HgCommand.java:4027)
	at org.netbeans.modules.mercurial.util.HgCommand.access$000(HgCommand.java:115)
	at org.netbeans.modules.mercurial.util.HgCommand$1.call(HgCommand.java:3923)
	at org.netbeans.modules.mercurial.util.HgCommand$1.call(HgCommand.java:3920)
	at org.netbeans.modules.mercurial.util.HgCommand.execEnv(HgCommand.java:3932)
	at org.netbeans.modules.mercurial.util.HgCommand.execForVersionCheck(HgCommand.java:4248)
	at org.netbeans.modules.mercurial.util.HgCommand.getHgVersion(HgCommand.java:717)
	at org.netbeans.modules.mercurial.Mercurial.checkVersionIntern(Mercurial.java:237)
	at org.netbeans.modules.mercurial.Mercurial.access$000(Mercurial.java:84)
	at org.netbeans.modules.mercurial.Mercurial$3.run(Mercurial.java:228)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1432)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2042)

in the logfile looks suspicious
Comment 3 Miloslav Metelka 2013-11-18 09:03:51 UTC 
Thanks markiewb.
After OutOfMemoryError the IDE may function improperly and it should be restarted ASAP.
 There might be a memory leak that could lead to the OOME but I would need a heap dump of the running IDE after the OOME gets thrown (possibly see http://wiki.netbeans.org/FaqMemoryDump )
 If the problem happens again please take and attach the heap dump and reopen the issue. Thanks.