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 14071 - Deadlock during startup (MediaTracker race condition)
Summary: Deadlock during startup (MediaTracker race condition)
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: rmatous
URL:
Keywords:
: 14391 20235 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-07-31 14:32 UTC by _ pkuzel
Modified: 2008-12-22 16:05 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (5.89 KB, text/plain)
2001-07-31 14:33 UTC, _ pkuzel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ pkuzel 2001-07-31 14:32:37 UTC
IDE Versioning        = IDE/1 spec=1.27 impl=200107311059

What is the MediaTracker waiting for?
Comment 1 _ pkuzel 2001-07-31 14:33:28 UTC
Created attachment 2017 [details]
Thread dump
Comment 2 Jan Zajicek 2001-08-01 13:53:11 UTC
Not sure, but shouldn't be
org.openide.loaders.InstanceNode.toBufferedImage replanned into AWT?
Comment 3 Vitezslav Stejskal 2001-08-03 01:04:39 UTC
How did you get this deadlock? Can I reproduce it somehow?
Comment 4 David Simonek 2001-08-03 08:08:27 UTC
Petr, did you look at the sources of MediaTracker?
I believe both MediaTrackers are waiting for images to be loaded, and
didn't receive correct notifications from image loader, maybe image
loader thread died somehow? I would say accessing MediaTracker from
several threads is correct here, as MediaTracker is asynchronous
itself (and methods are sync'd).
It's beyond Netbeans scope IMO, needs consultation with JDK team.
Comment 5 support 2001-08-03 09:43:16 UTC
Vitek: I can not reproduce it.
Dafe: Exactly I am missing the thread. It must die somehow.
Comment 6 Vitezslav Stejskal 2001-08-03 11:18:06 UTC
As long as it isn't reproducible I decrease priority to P3. If there 
are objections, please increase it again.
Comment 7 _ pkuzel 2001-08-07 16:54:25 UTC
Got it including a symptom (an exception that killed the thread):

     [exec]
MIMEResolverImpl.findMIMEType(org/netbeans/examples/lib/timerbean/timer.gif)
     [exec] Uncaught error fetching image:
     [exec] java.lang.NullPointerException
     [exec]     at java.util.zip.Inflater.reset(Inflater.java:253)
     [exec]     at java.util.zip.ZipFile.getInflater(ZipFile.java:249)
     [exec]     at
java.util.zip.ZipFile.getInputStream(ZipFile.java:197)
     [exec]     at
java.util.zip.ZipFile.getInputStream(ZipFile.java:174)
     [exec]     at
java.util.jar.JarFile.getInputStream(JarFile.java:307)
     [exec]     at
org.openide.filesystems.JarFileSystem.inputStream(JarFileSystem.java:450)
     [exec]     at
org.openide.filesystems.JarFileSystem$Impl.inputStream(JarFileSystem.java:1012)
     [exec]     at
org.openide.filesystems.AbstractFileObject.getInputStream(AbstractFileObject.java:165)
     [exec]     at
org.openide.filesystems.FileURL.getInputStream(FileURL.java:131)
     [exec]     at
sun.awt.image.URLImageSource.getDecoder(URLImageSource.java:112)
     [exec]     at
sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:251)
     [exec]     at
sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:217)
     [exec]     at
sun.awt.image.ImageFetcher.run(ImageFetcher.java:185)
Comment 8 Vitezslav Stejskal 2001-08-07 18:45:02 UTC
It looks like problem in JarFileSystem, Radek could you look at it, 
please.
Comment 9 rmatous 2001-08-16 14:33:18 UTC
Partly fixed: In JarFileSystem.getInputStream is NullPointerException 
catched and converted to FileNotFoundException. Then ImageFetcher 
won`t be killed because of uncaught exception - then 
MediaTracker.waitForID won`t be blocked. Then deadlock should not 
occure. Probably proper icon won`t be presented to user so I decrease 
priority to P4. 
Comment 10 akemr 2001-08-20 08:34:35 UTC
*** Issue 14538 has been marked as a duplicate of this issue. ***
Comment 11 dmladek 2001-08-20 10:19:39 UTC
Radek: in which build your fix should appear?
I reproduce it on Friday "Q-build" testing [NBdev-200108170100]
and fired the new issue #14538
Ales marked it as duplicate of this one....

If your fix has been already in Friday Q-build, could it be increased
the priority to P3?
Comment 12 rmatous 2001-08-20 14:03:54 UTC
Petr Kuzel found that this bug is already reported in BugParade: 
4336753. FYI: 
http://developer.java.sun.com/developer/bugParade/bugs/4336753.html.
Comment 13 Tomas Pavek 2001-10-18 15:08:46 UTC
*** Issue 14391 has been marked as a duplicate of this issue. ***
Comment 15 Tomas Pavek 2002-02-07 10:56:09 UTC
*** Issue 20235 has been marked as a duplicate of this issue. ***
Comment 16 Quality Engineering 2003-07-01 15:47:45 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 17 Quality Engineering 2003-07-01 16:36:34 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.