... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mac OS 10.9.4 / Java 8.20 / Windows resize not possible
#1
Hi,
I can launch the app but then I can hardly change the size of the window or the dimensions of the "frames".
I mostly get the beach ball and after a loooong time not much is happening.

RoutConverter Version 2.13.2
Reply
#2
Hi mabu,

it seems something is taking a lot of processing time. Since I don't own a Mac, I have no idea what beach ball means and what the expected behaviour is. Please checkout the code and debug, where the problem lies.
--
Christian
Reply
#3
I checked the console and found the following messages:
01.09.14 22:50:51.390 JavaApplicationStub[1178]: _createMenuRef called with existing principal MenuRef already associated with menu
01.09.14 22:50:51.401 JavaApplicationStub[1178]: (
0 CoreFoundation 0x00007fff97d8325c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff908d8e75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff97d8310c +[NSException raise:format:] + 204
3 AppKit 0x00007fff968a6cf4 -[NSCarbonMenuImpl _createMenuRef] + 62
4 AppKit 0x00007fff968a66ca -[NSCarbonMenuImpl _instantiateCarbonMenu] + 143
5 AppKit 0x00007fff968a4e92 -[NSApplication finishLaunching] + 876
6 libawt.jnilib 0x00000001158dccfe -[NSApplicationAWT finishLaunching] + 641
7 libswt-pi-cocoa-4332.jnilib 0x00000001185759ee Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSendSuper__Lorg_eclipse_swt_internal_cocoa_objc_1super_2J + 89
8 ??? 0x000000010ce2deee 0x0 + 4511162094
)
01.09.14 22:50:52.000 kernel[0]: JavaApplicationS (map: 0xffffff801d298c30) triggered DYLD shared region unnest for map: 0xffffff801d298c30, region 0x7fff90e00000->0x7fff91000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
01.09.14 22:56:42.000 kernel[0]: WinAppHelper (map: 0xffffff801b6f95a0) triggered DYLD shared region unnest for map: 0xffffff801b6f95a0, region 0x7fff90e00000->0x7fff91000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

I hope this help- and meaningful for you
Reply
#4
It seems to related to the creation of the menu. Sorry, I have no idea how to solve it. Play around with the command line arguments passed to the JVM.
--
Christian
Reply
#5
The ball is the same like the sand clock on windows. It shows, that the system is working a lot. In most cases, sth. is going wrong or need a lot of cpu-power. By the way, the resize of the google maps window doesn't work. I'll write a separate thread later on.
Reply
#6
(09.11.2014, 13:29)ryanthara Wrote: By the way, the resize of the google maps window doesn't work. I'll write a separate thread later on.

I've had reports on this. Most users claimed that minimizing/maximizing the window helped.
--
Christian
Reply
#7
Strange behaviour. Before the first minimize I can larger the window by mouse pulling just around 20 pixel. Then I have to do the next step, on and on...

After a couple of times it is really slow, but still in full view. But the program is so slow, you can not work with it.
Reply
#8
So you're experiencing what some users are describing. I guess it's connected to the Eclipse SWT integration and Mac OS X speciality with the first thread that has to contain the event loop.
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)