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.
Start Netbeans, open a DTD, click print, choose printer, whammo... NetBeans is gone. I tried printing an XML file just before that, and it worked. I tried both 4.0 and 4.1EA2. Hmmm... recheck: I restarted NetBeans, and it complains about an unclean shutdown or else another urnning instance. Click OK. Open some other DTD, now it works. Open some other files, no problems. Open the original DTD, prints ok. Windows XP with Suns JDK 1.5.0_01, Subversion
sounds like a jvm bug to me. do you still have the log files ($nb_userdir/var/log/messages.log)? can you attach it to the bug? is your usecase reproducible with the same dtd? or was it just a one time crash? reassigning to xml for evaluation. Do you guys do something special when printing or use the openide's action as is?
Created attachment 20346 [details] log file for today
As I wrote, my later attempts at printing succeeded, so I'm not sure how to reproduce. I'll try a reboot (hey, its windows) and a fresh session later on.The log file shows nothing apart from the starting of modules. I just atached the today part. Yesterday's log is full of InvocationTargetException entries... I tried mounting an OASIS Catalog and it fails the new XML file wizard. Both 4.1 EA2 and 4.0 showed similar behaviour. Is 1.4.2 or 1.5 the preferred platform for NetBeans itself?
Without reprodicible case it is no P2. Downgrading to P3. Please let us know if you will see it next time. Reproducible steps would help a lot ;-). Thanks.
This morning I carefully redid what I did yesterday, but everything worked beautifully. Just now back from getting a cup of coffee, made some changes in the DTD, print... whammo. Doesn't really count as reproducible, does it? I'll see if Sun has anything on crashes after printing. (yes, the printout came out fine)
Correction! the printout was not ok. It appears to crash during the print job. A Job shows up in the printer queue, but no pages come out.
The XML modules do nothing specific when printing DTD document.
More info: restarting the IDE and immediately trying to print the same file again will crash agin. Restart once more and print another file... ok. Print that DTD... ok. Something in the printing code that doesn't clean up correctly. What gets done after printing that could be construed as being needed to get a clean printing environment? Something in the formatting of DTDs? Java file was fine, after that the DTD was also??? Just rambling I suppose.
If the IDE just disappears, it have to be a bug in the JVM. It may be trigerred by some interaction of the printed data with the printing library or something. Anyway, we can't do much about it from NB.