sometimes nickcrash on different computers

[GoogleCodeExporter]

a nickcrash goes sometimes on different computers when Windows starting.
kouchat.lnk placed in "C:\users\user\main menu\Programs\Startup\".
lnk contains: C:\WINDOWS\system32\javaw.exe -Duser.name=%COMPUTERNAME% -jar 
kouchat.jar --minimized
kouchat.ini placed in C:\Users\user\.kouchat\ and contains:
nick=
owncolor=-15987646
syscolor=-16759040
logging=false
sound=true
browser=C:/Program Files (x86)/Mozilla Firefox/firefox.exe
smileys=true
lookAndFeel=Windows
balloons=false
networkInterface=Auto

screenshot attached

Windows 7 x64 pro kouchat 1.3.0

Original issue reported on code.google.com by mikum...@ya.ru on 17 Nov 2014 at 1:57

Attachments:

• error.jpg

[GoogleCodeExporter]

as it turned out it does so, sometimes kouchat starts and shows no icon in the 
tray, but hanging in the processes under the name of javaw.exe, the user is not 
seeing the chat starts it again. there are two processes of Java, first started 
with the name of the computer but without a GUI and a second process with a 
graphical interface but with the wrong name in chat. What could be wrong?

Original comment by mikum...@ya.ru on 17 Nov 2014 at 2:05

[GoogleCodeExporter]

process list

Original comment by mikum...@ya.ru on 17 Nov 2014 at 2:06

Attachments:

• list.txt

[GoogleCodeExporter]

I'm not sure what could be the issue. I have not had similar problems myself.

You could perhaps start KouChat with java.exe instead of javaw.exe to look for 
errors in the command prompt window when it happens.

Original comment by blu...@gmail.com on 18 Nov 2014 at 6:23

• Added labels: Type-Defect, OpSys-Windows

[GoogleCodeExporter]

1. it can be kaspersky influence to kouchat. when kouchat is started it remains 
in memory about 60mb while kouchat.jar file is only 0.5mb. can you decrease 
memory kouchat usage?
2. could you wrote me exact command with java.exe include "start minimized" and 
"computername as nick" parameters?
3. the reason could be in a slow Windows network initialization when user 
autologon is used, is there any java command for delaying apps start?

Original comment by mikum...@ya.ru on 18 Nov 2014 at 8:27

[GoogleCodeExporter]

1. Might be. I used NOD32 a few years back, and it killed KouChat when sending 
messages. Regarding memory usage, is 60mb a problem? Doesn't seem much to me.

2. It's the exact same command you used before, but with java.exe instead of 
javaw.exe. Based on your details at the top it's probably:
C:\WINDOWS\system32\java.exe -Duser.name=%COMPUTERNAME% -jar kouchat.jar 
--minimized

3. Not that I know of. You could try experimenting with something like this:
http://superuser.com/questions/680322/add-delay-to-desktop-shortcut

Original comment by blu...@gmail.com on 19 Nov 2014 at 1:02

[GoogleCodeExporter]

1. the problem is that nobody cares how much resource consuming program, or 
rather such freaks like autodesk and microsoft is profitable. This is wrong. Of 
course, talking about kouchate it is not so important.
2. this command gives command line window, screenshot attached
3. thanks

Original comment by mikum...@ya.ru on 19 Nov 2014 at 1:33

Attachments:

• windows.jpg

[GoogleCodeExporter]

1. I agree. Java has some memory overhead though. It's difficult to get memory 
usage lower than it already is.

2. It looks like everything is OK in that screenshot. Can you get a screenshot 
when KouChat has failed to start properly?

Original comment by blu...@gmail.com on 19 Nov 2014 at 6:25

[GoogleCodeExporter]

ok. Screenshot shows that unwanted window is appear when java.exe used instead 
of javaw.exe.

Original comment by mikum...@ya.ru on 19 Nov 2014 at 8:17

[GoogleCodeExporter]

That is correct. You need to look for errors in that window.
If you find an error, you can let me know, and revert back to javaw.exe.

Original comment by blu...@gmail.com on 21 Nov 2014 at 11:10

[GoogleCodeExporter]

users don't need that window. am i right?

Original comment by mikum...@ya.ru on 21 Nov 2014 at 11:45

[GoogleCodeExporter]

Those who are trying to reproduce the problem need that window.

Original comment by blu...@gmail.com on 21 Nov 2014 at 12:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

ie, you offer to show it to all users box until it seems some sort of useful 
information?

Original comment by mikum...@ya.ru on 21 Nov 2014 at 12:56

[GoogleCodeExporter]

That would probably be the quickest way.

Original comment by blu...@gmail.com on 21 Nov 2014 at 12:58

[GoogleCodeExporter]

The first step to solving the problem should be the prevention of secondary 
copies run kouchat into memory. there will be no errors nickcrash. While I did 
not find the situation to find out why a user starts a chat for the second 
time. I think this week will see.

Original comment by mikum...@ya.ru on 24 Nov 2014 at 1:18

[GoogleCodeExporter]

Preventing a second instance of KouChat might not help in this situation. If 
it's crashed, then you would have to kill the old before you can start the new.

Original comment by blu...@gmail.com on 25 Nov 2014 at 5:26

[GoogleCodeExporter]

nickcrash occurs because two or more copies of the program can not operate 
simultaneously.

Original comment by mikum...@ya.ru on 25 Nov 2014 at 6:21

[GoogleCodeExporter]

KouChat supports up to 50 instances running on the same computer. Nick crash is 
a feature that makes sure that the nick name is unique across instances.

Stopping a second instance from starting will not help if the first instance 
has crashed. It will not "uncrash" the first instance.

Original comment by blu...@gmail.com on 25 Nov 2014 at 6:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

ok, let it be a feature.

Original comment by mikum...@ya.ru on 25 Nov 2014 at 9:04

[GoogleCodeExporter]

I found out that under heavy load on the computer (CPU) attempts to open a chat 
window somehow trigger the secondary instance of the program. Maybe we should 
make a pop-up window that appears when you start to secondary instance of the 
program, such as "One instance of the kouchat is already running, you want to 
start another one?".
And one more question, is it difficult to get the "X" button (close) to operate 
as "_" (minimize)?

Original comment by mikum...@ya.ru on 26 Nov 2014 at 8:18

[GoogleCodeExporter]

How are you opening a chat window to get a second instance?
Do you mean users who are impatient, and clicking several times on the shortcut?

I can have a look into making some kind of "single instance mode" when I have 
time. 
I'm still working on language support.

Why would you want to minimize with "X" instead of "_"? If you want to minimize 
quick, just press escape.

Original comment by blu...@gmail.com on 27 Nov 2014 at 6:22

[GoogleCodeExporter]

I think yes. some user told me that he launched second instance because he 
didn't see icon of first instance at systray. But i still cant repeat bug.

ok, thanks!

I mess with "minimize" because user behavior still as with previous old chat 
"netter". In that chat "X" button operates as "_".

Original comment by mikum...@ya.ru on 27 Nov 2014 at 8:55

[GoogleCodeExporter]

OK. So the bug has not been reproduced yet.

And X to minimize is just old habit?
Users can minimize with "_", escape and the minimize button below the user 
list. 
I don't see the need for a fourth way to minimize as well.

Original comment by blu...@gmail.com on 1 Dec 2014 at 8:30

[GoogleCodeExporter]

bug appears periodically on one of the 50 computers a couple of times a week. I 
find it difficult to catch it. I notice it in the general chat board on a 
computer that is always on.

about minimizing I realized, ок.

Original comment by mikum...@ya.ru on 1 Dec 2014 at 8:53

[GoogleCodeExporter]

A couple of times a week is quite often. Have you setup that computer to use 
java instead of javaw, to see if there are any errors?

Original comment by blu...@gmail.com on 2 Dec 2014 at 9:37

[GoogleCodeExporter]

I work remotely on a few companies, too many questions for me to be. "What is 
this black window, and suddenly it's a virus?" I'm not ready for this.

Original comment by mikum...@ya.ru on 2 Dec 2014 at 10:24