File menu broken in 2014.02

Question

Premiere Pro has been locking up when i go to the file menu after playing a video. The menu will not display or will show an application isn't responding error.
All the other menus work apart from the File menu, When i have attempted to get a screenshot of the problem happening the print screen function also stops working. (all functionality stops working when the file menu is open causing the OS to grind to a hault, this feels like a memory leak.)
What have i done?
Reinstalled Adobe Premiere (Clean install using the uninstaller tool.)
Reinstalled the drivers using a clean installation.
Reinstalled depedencies such as Quicktime and VCs.
What version of Premiere Pro? Include the minor version number (e.g., Premiere Pro CS5.5 with the 5.5.2 update).:  8.2.0 (65) build (Premiere Pro CC 2014.2)
Have you installed the recent updates? (If not, you should. They fix a lot of problems.) Yes.
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac". Win 8.1 64 bit
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime". H.264 in a mp4 container.
If you are getting error message(s), what is the full text of the error message(s)? No. (Just having lock ups)
What were you doing when the problem occurred?  (Playing a video followed by trying to go to the file menu. the file menu drops down however the file menu isn't displaying. This can make the device lock up completely while it waits for a response from Premiere Pro CC.)
Has this ever worked before?  Yes (for a very long time!)
What other software are you running?  N/A
Do you have any third-party effects or codecs installed?  N/A
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU). N/A
Are you using Mercury Playback Engine GPU Acceleration?  Yes using the latest 347.09 driver set.
Does the problem only happen with your final output, with previews, or both? this affects the program.

Answer 1

H:\java\misc\forums>java CurDir
H:\java\misc\forums exists? false
H:\java\misc\forums exists? true
public class CurDir
     public static void main(String [] arg) {
          File curdir = new File("");
          curdir = new File(curdir.getAbsolutePath());
}I think what may be happening here is that, in the first case, you are selecting a file named "" in the current directory (not the directory itself). The absolute path name of this is then given as a string: "H:\java\misc\forums\" + "" (directory + file name). However, this string (when concatenated) represents a directory in the second case. That is, the second one is the current directory, while the first one is a file "" in the current directory ("" would not be a valid file). Internally, File contains a name sequence, representing the hierarchy of directory and file names. My guess is that in one case the hierarchy is {"H:", "java", "misc", "forums", ""} and the other {"H:", "java", "misc", "forums"}; see the difference?
You can test this out using File.getName() or File.getParent() to see if they represent different things:
File firstFile = new File("");
File secondFile = new File(firstFile.getAbsolutePath());
System.out.println("Name of first file:    " + firstFile.getName());
System.out.println("Name of second file:   " + secondFile.getName());
System.out.println("Parent of first file:  " + firstFile.getParent());
System.out.println("Parent of second file: " + firstFile.getParent());If you are looking to get the current directory, you may want to use "." instead of "". Alternatively, you can get the current working directory from the system properties.