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 227501 - Netbeans crash when committing a change after resuming computer from sleep mode
Summary: Netbeans crash when committing a change after resuming computer from sleep mode
Status: RESOLVED DUPLICATE of bug 214767
Alias: None
Product: platform
Classification: Unclassified
Component: JDK Problems (show other bugs)
Version: 7.3
Hardware: Macintosh (x86) Mac OS X
: P2 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-15 05:22 UTC by eddiecarpenter
Modified: 2013-04-02 12:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The problem details and System configuration as reported my MacOSX (93.63 KB, text/plain)
2013-03-15 05:22 UTC, eddiecarpenter
Details
osx crash log (83.75 KB, application/octet-stream)
2013-03-16 12:43 UTC, jbracking
Details

Note You need to log in before you can comment on or make changes to this bug.
Description eddiecarpenter 2013-03-15 05:22:41 UTC
Created attachment 132632 [details]
The problem details and System configuration as reported my MacOSX

Netbeans crashes when trying to access the commit dialog after the machine was resumed from sleeping mode. This *always* happens on the first time one access the commit dialog. If Netbeans is then restarted everything works 100%
Comment 1 Ondrej Vrabec 2013-03-15 06:59:32 UTC
Application Specific Information:
*** CFRelease() called with NULL ***

Thread 0 Crashed:: AppKit Thread  Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation      	0x00007fff8dac97d8 CFRelease + 40
1   liblwawt.dylib                	0x0000000162400647 __Java_sun_lwawt_macosx_CWrapper_00024NSObject_release_block_invoke_1 + 91
Comment 2 jbracking 2013-03-16 12:43:16 UTC
Created attachment 132680 [details]
osx crash log
Comment 3 Antonin Nebuzelsky 2013-04-02 12:27:00 UTC

*** This bug has been marked as a duplicate of bug 214767 ***